| Server IP : 158.247.231.215 / Your IP : 216.73.217.84 Web Server : Apache/2.4.41 (Ubuntu) System : Linux CTMS 5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC 2025 x86_64 User : www-data ( 33) PHP Version : 8.0.30 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,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /etc/cloud/clean.d/ |
Upload File : |
-- cloud-init's clean.d run-parts directory -- This directory is provided for third party applications which need additional configuration artifact cleanup from the filesystem when the command `cloud-init clean` is invoked. The `cloud-init clean` operation is typically performed by image creators when preparing a golden image for clone and redeployment. The clean command removes any cloud-init semaphores, allowing cloud-init to treat the next boot of this image as the "first boot". When the image is next booted cloud-init will performing all initial configuration based on any valid datasource meta-data and user-data. Any executable scripts in this subdirectory will be invoked in lexicographical order with run-parts by the command: sudo cloud-init clean. Typical format of such scripts would be a ##-<some-app> like the following: /etc/cloud/clean.d/99-live-installer