auto-starting daemons on startup

[R Shapiro]

Stefan Jeglinski writes:
 > As an example, I'd like to add proftpd to the startup.=20
 > ...
 > I suppose this is all well and good. BTW, I run proftp in standalone=
=20
 > mode, no [x]inet.

Just out of curiosity, why don't want use xinetd here?



 > Now, if I run ntsysv, proftp does not show up at all. Also:
 >=20
 > root@orion rc3.d]# chkconfig --list proftp
 > service proftp does not support chkconfig

To be honest, I've never needed to add a new init.d entry, so I don't
have direct experience with this.  But I think the chkconfig man page
has the answer:

       Each service which should be manageable by chkconfig needs
       two or more commented lines added to  its  init.d  script.
       The  first line tells chkconfig what runlevels the service
       should be started in by default, as well as the start  and
       stop  priority  levels.  If  the  service  should  not, by
       default, be started in any runlevels, a - should  be  used
       in  place of the runlevels list.  The second line contains
       a description for the service, and may be extended  across
       multiple lines with backslash continuation.

       For example, random.init has these three lines:
       # chkconfig: 2345 20 80
       # description: Saves and restores system entropy pool for \
       #              higher quality random number generation.
       This says that the random script should be started in lev=AD
       els 2, 3, 4, and 5, that its start priority should be  20,
       and  that  its  stop priority should be 80.  You should be
       able to figure out what the description says; the \ causes
       the line to be continued.  The extra space in front of the
       line is ignored.

This will probably fix the ntsysv problem as well.


--=20
rshapiro@bbn.com