HEX
Server: nginx/1.24.0
System: Linux localhost 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64
User: www (1000)
PHP: 8.3.27
Disabled: passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,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_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv
Upload Files
File: //lib/systemd/system/cloud-config.target
# 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