1838243 Members
6149 Online
110125 Solutions
New Discussion

rc.log

 
SOLVED
Go to solution
Omar Alvi_1
Super Advisor

rc.log

Hi,

What is the significance of the status SKIPPED in the /etc/rc.log? Is it something to be concerned about ... occuring for any of the run levels? What if this entity is something required to be running on the system?

Regards,

-Alvi
3 REPLIES 3
Jean-Louis Phelix
Honored Contributor
Solution

Re: rc.log

Hi,

It only means that this script has been skipped without executing, for example because the corresponding variable in the /etc/rc.config.d/ is set to 0. The intearctive menu will show "N/A". Have a look to the header of /sbin/init.d/template :

# Allowed exit values:
# 0 = success; causes "OK" to show up in checklist.
# 1 = failure; causes "FAIL" to show up in checklist.
# 2 = skip; causes "N/A" to show up in the checklist.
# Use this value if execution of this script is overridden
# by the use of a control variable, or if this script is not
# appropriate to execute for some other reason.
# 3 = reboot; causes the system to be rebooted after execution.
# 4 = background; causes "BG" to show up in the checklist.
# Use this value if this script starts a process in background mode.

Regards.
It works for me (© Bill McNAMARA ...)
Rajeev  Shukla
Honored Contributor

Re: rc.log

Hi,

Skiped means something not configured by you. And you should ignore that.
Say if you haven't configured NIS then during startup or in rc.log you'll see NIS service as skiped.

Cheers
Rajeev
Chris Hulihan
Advisor

Re: rc.log

Just to expand on Jean-Louis's answer (which is good)... Basically this allows you to keep the link to the startup scripts where they are, but just put the flag in so that it bypasses the commands (for example, we have a couple of apps, oracle, etc. that run by default and when we're doing server work and don't want these to come up, we can just change the corresponding files in /etc/rc.config.d/* for the application so we don't have to manually shut down the application after a reboot. Then when we're done with the work that requires a few reboots, we'll update this file again so that the scripts are not bypassed. This way if someone forgets to turn this back "on" it's a little easier to catch than if it did not run at all.

Chris