On Fri, 2002-06-14 at 14:13, Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>,
> Ross Boylan <[EMAIL PROTECTED]> wrote:
> >By the way, I'm not sure what the success thing was in the stop case
> >below; I got errors when I tested it and removed it from my script.
>
> That's because t
In article <[EMAIL PROTECTED]>,
Ross Boylan <[EMAIL PROTECTED]> wrote:
>By the way, I'm not sure what the success thing was in the stop case
>below; I got errors when I tested it and removed it from my script.
That's because the example was actually a redhat example.
A standard init.d template c
> What's the best way to run a script once on startup and again (well, a
> related script) on shutdown? I want to run the scripts as a user rather
> than root, which I believe is the standard init.d method.
your script could read:
#!/bin/sh
# /etc/init.d/myscript
# references /etc/init.d/mystart
Thanks, that's what I needed.
After consulting the policy manual, I decided the right thing was
for the script to execute on entry into level S and exit for levels
0 and 6. The incantation for the script MSGateway is
update-rc.d MSGateway start 90 S . stop 15 0 6 .
reflecting my judgement I
On Thu, 2002-06-13 at 21:13, Ross Boylan wrote:
> What's the best way to run a script once on startup and again (well, a
> related script) on shutdown? I want to run the scripts as a user
> rather than root, which I believe is the standard init.d method.
Since you (presumably) know about init.d &
What's the best way to run a script once on startup and again (well, a
related script) on shutdown? I want to run the scripts as a user
rather than root, which I believe is the standard init.d method.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
6 matches
Mail list logo
