I'm surprised nobody mentioned tksysv, which is my favorite. - jos
At 08:49 PM 4/17/2000 -0500, Ed Alexander wrote:
Philippe,
When switching to a given runlevel, scripts are
executed in alphanumeric order by their names within
the /etc/rc.d/rc#.d directory. For example K0...,
K1..., etc., then
Philippe,
When switching to a given runlevel, scripts are
executed in alphanumeric order by their names within
the /etc/rc.d/rc#.d directory. For example K0...,
K1..., etc., then S0... S1..., etc. So, to ensure a
script is run at the proper time in the sequence,
simply name it so that it
BTW, I have one question about this organization : how do you control the order in
which scripts are executed at a given runlevel ?
Thanks
Philippe
Wayne Dyer [EMAIL PROTECTED] writes:
Danny wrote:
Assuming I want to install sys progs without the RPMS I was wonder why the
developers
The name of the symbolic link controls that S15* will run before S20* or S40atd will
run before S40cron
The script that runs these is /etc/rc.d/rc and it uses a for loop contruct to iterate
through the files (links) in the given runlevel
directory.
Having read this thread I got curious and
Philippe Moutarlier wrote:
BTW, I have one question about this organization : how do you control the order in
which scripts are executed at a given runlevel ?
Each of the symlinks has a three character prefix which tells "init"
what to do with it. The first character is either a "S" or a
At 10:23 2000-04-16 -0600, Philippe Moutarlier wrote:
BTW, I have one question about this organization : how do you
control the order in which scripts are executed at a given runlevel ?
They're executed in alphabetical order by filename.
Tony
--
Anthony E. Greene [EMAIL PROTECTED]
On Sun, 16 Apr 2000, Philippe Moutarlier wrote:
BTW, I have one question about this organization : how do you
control the order in which scripts are executed at a given
runlevel ?
Look at the prefixes for the symbolic links. S is start, K is kill.
the number is the sequence, lowest being
At 10:23 AM 4/16/00 -0600, you wrote:
BTW, I have one question about this organization : how do you control the
order in which scripts are executed at a given runlevel ?
Thanks
Philippe
The name of the symlink in the /etc/rc.d/rc?.d directory controls the
order. For a given run level, the
From: Danny [EMAIL PROTECTED]
Assuming I want to install sys progs without the RPMS I was wonder why the
developers of RH have made modifying etc/rc.d so complex.
Whereas in BSD you have to only create a file called sysprogs.sh to start the
program up.
Put anything else you want started
On Fri, 14 Apr 2000, Danny wrote:
Assuming I want to install sys progs without the RPMS I was wonder why the
developers of RH have made modifying etc/rc.d so complex.
Whereas in BSD you have to only create a file called sysprogs.sh to start the
program up.
then add it to /etc/rc.d/rc.local
Danny wrote:
Assuming I want to install sys progs without the RPMS I was wonder why the
developers of RH have made modifying etc/rc.d so complex.
Whereas in BSD you have to only create a file called sysprogs.sh to start the
program up.
Between the BSD and SysV init style init scripts, I'll
At 06:59 PM 4/14/00 +1000, Danny wrote:
Assuming I want to install sys progs without the RPMS I was wonder why the
developers of RH have made modifying etc/rc.d so complex.
Whereas in BSD you have to only create a file called sysprogs.sh to start the
program up.
The main reason that it is
Danny wrote:
Assuming I want to install sys progs without the RPMS I was wonder why the
developers of RH have made modifying etc/rc.d so complex.
Whereas in BSD you have to only create a file called sysprogs.sh to start the
program up.
It uses the System V method. It's complex, but it has
Assuming I want to install sys progs without the RPMS I was wonder why the
developers of RH have made modifying etc/rc.d so complex.
Whereas in BSD you have to only create a file called sysprogs.sh to start the
program up.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the
14 matches
Mail list logo
