Oracle Linux 7: Service in /etc/init.d/ Does Not Start When It is a Symlink to Another Filesystem
(Doc ID 2431189.1)
Last updated on JUNE 24, 2020
Applies to:Linux OS - Version Oracle Linux 7.0 and later
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
A SysVINIT service in /etc/init.d/ does not start at the OS boot time when it is symbolic link to non-root filesystem. It leaves an error message "no such file or directory" in /var/log/messages.
For example, /etc/init.d/myservice is a symbolic link to /opt/bin/myservice, and /opt is a non-root filesystem.
|# ls -al /etc/init.d/myservice
lrwxrwxrwx. 1 root root 30 Aug 2 16:49 /etc/init.d/myservice.sh -> ../../../opt/bin/myservice.sh
# grep /opt /etc/fstab
UUID=c258ac10-41cf-4fe3-b2a1-14d5f916bdbe /opt xfs defaults 0 0
# grep myservice /var/log/messages
Aug 2 15:36:53 dhcp-10-188-220-41 systemd-sysv-generator: stat() failed on /etc/rc.d/init.d/myservice: No such file or directory
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document