No such file or directory /etc/init.d/functions

init-script

I created a startup script to start/restart/stop a group of applications. I used the lib /etc/init.d/functions in my script. It is working well on my system, but it not working for my client; he is getting the error:

No such file or directory /etc/init.d/functions

Right now I don't know which linux distro my client uses. Is the init.d/functions file different for different Linux distros? If so, how can I find it?

Best Answer

It's specific to whatever distribution you're running. Debian and Ubuntu have /lib/lsb/init-functions; SuSE has /etc/rc.status; none of them are compatible with the others. In fact, some distributions don't use /etc/init.d at all, or use it in an incompatible way (Slackware and Arch occur to me off the top of my head; there are others).

Related Solutions

Are certain parts of startup scripts necessary or just good practice

Look at the docs file /usr/share/doc/initscripts-*/sysvinitfiles (On current F14, /usr/share/doc/initscripts-9.12.1/sysvinitfiles). There's further documentation here: http://fedoraproject.org/wiki/Packaging/SysVInitScript.

The chkconfig line defines which runlevels the service will start in by default (if any), and where in the startup process they'll be ordered.

# chkconfig: <startlevellist> <startpriority> <endpriority>

        Required.  <startlevellist> is a list of levels in which
        the service should be started by default.  <startpriority>
        and <endpriority> are priority numbers.  For example:
        # chkconfig: 2345 20 80

And, note that this all becomes obsolete with Fedora 15 and systemd.

Linux – Connection Between /etc/init.d and /etc/rcX.d Directories

Let's forget init.d or rcx.d and keep things very simple. Imagine you were programming a program whose sole responsibility is to run or kill other scripts one by one.

However your next problem is to make sure they run in order. How would you perform that?

And lets imagine this program looked inside a scripts folder for running the scripts. To order the priority of scripts you would name them in lets say numerical order. This order is what dictates the relation between init.d and rc

In other words init.d contains the scripts to run and the rcX.d contains their order to run.

The X value in rcX.d is the run level. This could be loosely translated to the OS current state.

If you dig inside the rcX.d scripts you will find this formatting:

Xxxabcd

X is replaced with K or S, which stands for whether the script should be killed or started in the current run level
xx is the order number
abcd is the script name (the name is irrelevant however where it points is the script this will run)

Best Answer

Related Solutions

Are certain parts of startup scripts necessary or just good practice

Linux – Connection Between /etc/init.d and /etc/rcX.d Directories

Related Question