- Original Message -
From: "Crispin Wellington" <[EMAIL PROTECTED]>
To: "Debian Users" <[EMAIL PROTECTED]>
Sent: Tuesday, October 29, 2002 10:48 AM
Subject: Re: /etc/init.d services start/stop question
>>AFAIK...
>>
>>K's are called i
On Tue, 2002-10-29 at 08:46, Benedict Verheyen wrote:
> Hi,
>
> i just installed shorewall and it made 2 links in /etc/rc2.d
> K99shorewall and S99shorewall. I can see why the S99
> would have to be there. Is the reason of K99 to prevent
> net access for instance when one goes "telinit S"?
>
> Wh
On Tue, Oct 29, 2002 at 01:46:20AM +0100, Benedict Verheyen wrote:
Hello
> But how does the system specify these when i reads
> for instance S99shorewall when booting the system?
> Does it add a "start" parameter to the script when it
> resolves the link to start the script?
You will find a scr
On Tue, Oct 29, 2002 at 01:46:20AM +0100, Benedict Verheyen wrote:
> i just installed shorewall and it made 2 links in /etc/rc2.d
> K99shorewall and S99shorewall. I can see why the S99
> would have to be there. Is the reason of K99 to prevent
> net access for instance when one goes "telinit S"?
>
Hi,
i just installed shorewall and it made 2 links in
/etc/rc2.d
K99shorewall and S99shorewall. I can see why the
S99
would have to be there. Is the reason of K99 to
prevent
net access for instance when one goes "telinit
S"?
What scripts are called first, K or S?
Also, the debian refer
5 matches
Mail list logo