ÿØÿà JFIF ÿÛ „ ( %"1"%)+...383,7(-.-
![]() Server : LiteSpeed System : Linux v2202501248978307069 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64 User : voirf6718 ( 1002) PHP Version : 7.3.33-1+focal Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals, Directory : /lib/systemd/system/ |
# cloud-config.target is the earliest synchronization point in cloud-init's # boot stages that indicates the completion of datasource detection (cloud-id) # and the presence of any meta-data, vendor-data and user-data. # Any services started at cloud-config.target will need to be aware that # cloud-init configuration modules have not yet completed initial system # configuration of cloud-config modules and there may be race conditions with # ongoing cloud-init setup, package installs or user-data scripts. # Services that need to start at this point should use the directives # "After=cloud-config.target" and "Wants=cloud-config.target" as appropriate. # To order services after all cloud-init operations, see cloud-init.target. [Unit] Description=Cloud-config availability Wants=cloud-init-local.service cloud-init.service After=cloud-init-local.service cloud-init.service