On Thursday 16 May 2002 11:47 pm, drieux wrote:
[snip]
the problem is that it closes both stdin and stderr, which are
used by other things we play with and need to be appropriately
reopened to some place other than the terminal we are no
longer talking to...
I'm all in favor of cluttering
warning note: daemonology comes in two basic catagories
a) standard system type daemons
b) distributed networking solutions
AKA: OLTP systems, enterprise solutions, YourBuzzHere
for the first class syslog is ok enough - especially as gary
notes that one can
on Thu, 16 May 2002 19:16:58 GMT, Matt Simonsen wrote:
I have a script to monitor servers which is basically an infinate
loop that sleeps and runs again. I start from a ssh session by the
command:
ssh -f $server ~/script
It seems to be dieing on some of our busier servers.
I'm really
.
-Original Message-
From: Felix Geerinckx [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 3:45 PM
To: [EMAIL PROTECTED]
Subject: Re: proper way to start daemon
on Thu, 16 May 2002 19:16:58 GMT, Matt Simonsen wrote:
I have a script to monitor servers which is basically
From: Matt Simonsen[SMTP:[EMAIL PROTECTED]]
I have a script to monitor servers which is basically an infinate
loop that
sleeps and runs again. I start from a ssh session by the command:
ssh -f $server ~/script
It seems to be dieing on some of our busier servers.
I'm
On Thu, May 16, 2002 at 12:16:58PM -0700, Matt Simonsen wrote:
My best guess is I should have the script immediately fork a copy of itself
then die while the forked copy still runs, but I haven't been able to figure
out how to make that work. Any suggestions would be helpful, especially a
On Thursday, May 16, 2002, at 03:24 , Michael Lamertz wrote:
[..]
1. get out of the parent's (in that case your shell's) process group.
We'll have PPID 1 after this call. The only error that setsid can throw
is EPERM which means that we already are process group leader.
2. move up to the
