Actually, my problem turns out to be even more basic and foolish than
that. I assumed that since the relevant Kill files were present in the
ls listing, then the Start files would be, too. Nope. I had to make
those soft links; when I did, everything worked properly.
Then perhaps you still need to read up on how the startup scripts work,
at least on Fedora. The startup routine runs every link in the rcX.d
directory that has either an S or a K in the order determined by the
number contained in the name. On entering a runlevel, if the link is a
KXXservice then it runs the service with the stop argument, if the link
is a SXXservice then it runs it with a start, the order is from low
numbers to high. This procedure is reversed on leaving a runlevel, the
S = stop, the K = start (I believe) and the numerical order goes from
high to low. I need to read up on the docs myself since I cant tell you
if it does kills then starts or if it does all the numbers in order
regardless of the argument. I believe it is the former though.
The fact that samba works for you is a wonderful coincidence. By most
accounts, the default setup for samba is a K35/S65. In your setup that
means that samba gets killed and then started, leaving you with a
running system. If you had to change to another runlevel and expected
samba to be stopped you'd be in for a surprise.
This is exactly the reason that somebody made chkconfig, it keeps stuff
like this from happening. It also follows the convention that when a
service is switched from stop to start and vice versa, the number given
to it is 100-whatever the old number was, which is why samba is
usually a K35/S65.
Eric Hines
Forwarded Message
From: Paul Gienger [EMAIL PROTECTED]
snip
Date: Sun, 27 Feb 2005 19:21:12 -0600
ntsysv doesn't list the samba daemons (smbd, nmbd), and while I could
use chkconfig, it appears, to add the daemons, I'd rather do this via
the rcx.d links so I can understand what's going on.
Read up exactly what chkconfig does (man chkconfig). It just moves the
links around for you automatically so that locations and such are sane
and verifiable.
Eric Hines
Forwarded Message
From: Sp0oKeR Labs [EMAIL PROTECTED]
snipDate: Sun, 27 Feb 2005 21:35:32 -0300
Did u try ntsysv ou chkconfig? Are you using SELinux?
Regards,
On Sun, 27 Feb 2005 18:29:55 -0600, E E Hines [EMAIL PROTECTED] wrote:
Greetings,
Running FC3, kernel 2.6.9-1.667.i686, Samba v 3.0.11.
I have been able to guts up Samba by adding a procedure
to /etc/rc.d/rc.local, but I can't get the system to start from
the /etc/rc.d/rcx.d directories. I have an smb script
in /etc/rc.d/init.d that is soft-linked from the rcx.d directories, and
that runs just fine when I invoke it from the command line, but
apparently the rcx.d links aren't getting called at all.
Any suggestions would be greatly appreciated.
Thanks
Eric Hines
--
Dawn is nature's way of telling you to go to bed.
And to stay there until the evil yellow disk is gone again.
--Anonymous
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--
--
Paul GiengerOffice: 701-281-1884
Applied Engineering Inc.
Systems Architect Fax:701-281-1322
URL: www.ae-solutions.com mailto: [EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
