| Server IP : 13.213.54.232 / Your IP : 216.73.216.72 Web Server : Apache/2.4.52 (Ubuntu) System : Linux ip-172-31-17-110 6.8.0-1029-aws #31~22.04.1-Ubuntu SMP Thu Apr 24 21:16:18 UTC 2025 x86_64 User : www-data ( 33) PHP Version : 7.1.33-67+ubuntu22.04.1+deb.sury.org+1 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, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /proc/self/root/lib/systemd/system/ |
Upload File : |
# 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