Centos – Starting a daemon automatically from init.d

bootcentosinit.dstartup

I installed vnstats to see bandwidth statistics, I copied an init.d file tempalte, I placed it in init.d directory, it works ok to access this file and do start/restart/status, but this file should start automatically on system boot, correct? It doesn't start, how can I debug this?
If after system boot I do init.d/vnstat then it starts.

I am running Centos 5

Thank you.

Best Answer

If you write an init script with the correct syntax, you can turn it into a service:

chkconfig --add vnstats

after that, you can turn it on or off for certain runlevels:

chkconfig --level 345 vnstats on

You can also manually start or stop services with the service command, using the functions declared in the script itself. For example, if your script has a function called stop and one called start, you can use

service vnstats stop and service vnstats start

Suggested reading: the official documentation

Related Solutions

Linux – chkconfig not starting application script on bootup

chkconfig essentially makes a symlink from, say, /etc/rc3.d/S85myapp to /etc/init.d/myapp. Verify that those links exist. I assume they do, since the "chkconfig --list" is showing that they're "on".

Since you can execute /etc/init.d/myapp from prompt, but it doesn't occur during startup, my guess is that there's an issue with the PATH, or that a service that you need up and running before executing myapp is actually initializing after myapp. Remember that the scripts in /etc/rc3.d (or whatever your initial runlevel is) are executed in sort order. Verify that myapp has everything it needs to run.

(My guess it that there's a PATH issue, though)

Debian – init.d script not working

In case your init script has no symlinks in the rc*.d directories run the following to create them:

update-rc.d tightvncserver defaults

Best Answer

Related Solutions

Linux – chkconfig not starting application script on bootup

Debian – init.d script not working

Related Topic