| Server IP : 20.75.53.88 / Your IP : 216.73.217.138 [ Web Server : Apache System : Linux VMRALP-3 4.4.0-256-generic #290~14.04.1-Ubuntu SMP Thu Jun 20 09:24:50 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29+esm15 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,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, Domains : 3 Domains MySQL : ON | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /proc/self/root/proc/13570/root/proc/thread-self/root/etc/init/ |
Upload File : |
# plymouth-ready - send an event to indicate plymouth is up
#
# This job notifies that the plymouth splash screen is up, either started
# from the initrd or when the 'plymouth-splash' job starts. The login
# managers use the event to avoid a race with plymouth-splash:
#
# https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/982889
description "Send an event to indicate plymouth is up"
task
start on startup or started plymouth-splash
instance $UPSTART_EVENTS
emits plymouth-ready
script
if [ "$UPSTART_EVENTS" = started ] || \
status plymouth-splash | grep -q "start/started" || \
plymouth --ping
then
initctl emit plymouth-ready
fi
end script