[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: init.d

On Mon, Jul 24, 2000 at 12:03:17AM +0000, R K wrote
> I've been having some problems getting startup scripts to work.  
> Particularly with MySQL (latest binary release).  From what I know, you're 
> supposed to put the script in /etc/init.d and make a sym-link to /etc/rcX.d 
> right?  In any case, I put the script in init.d and made a symlink 
> (S99mysql.server -> ../init.d/mysql.server) in rc3.d, but nothing happens at 
> startup.  I remeber having this problem before and fixing it, but now I 
> can't remember what I did.  Running potato (not like it makes a difference, 
> I was running slink the other time).  Anyway, if I've missed some critical 
> step, please let me know. =)
> Oh yeah.. the script and the symlink DO work directly from the command line. 
> i.e. "/etc/init.d/mysql.server start" works.  I've even tried echo testing 
> the script, and have determined that it's not even being run at startup.

Scripts in the Debian init.d directories are run using
run-parts. Run-parts ignores scripts that don't conform to
certain naming conventions:

       run-parts runs a number of scripts or programs found in  a
       single  directory  directory.   Filenames  should  consist
       entirely of upper and lower case letters,  digits,  under-
       scores,  and  hyphens.   Subdirectories  of  directory and
       files with other names will be silently ignored.

So, you shouldn't use "." in script names.  This means that if
you leave any backup files lying around (e.g., mysql-server.bak,
mysql-server~, #mysql-server#, etc.) they won't be inadvertently

John P.
http://www.mdt.net.au/~john Debian Linux admin & support:technical services

Reply to: