From owner-freebsd-questions Sun Jul 30 17:27: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from zaphod.universalregistrations.com (universalregistrations.com [203.23.167.231]) by hub.freebsd.org (Postfix) with SMTP id 3DD1737B712 for ; Sun, 30 Jul 2000 17:27:00 -0700 (PDT) (envelope-from luke@neither.apana.org.au) Received: (qmail 1409 invoked from network); 31 Jul 2000 00:27:00 -0000 Received: from unireg-gw.melbourne.austasia.net (HELO pc21.neither.apana.org.au) (203.23.160.199) by universalregistrations.com with SMTP; 31 Jul 2000 00:27:00 -0000 Received: (qmail 11187 invoked from network); 31 Jul 2000 00:26:46 -0000 Received: from unknown (HELO pc26.neither.apana.org.au) (192.168.20.26) by 192.168.20.25 with SMTP; 31 Jul 2000 00:26:46 -0000 Received: by FENCHURCH with Internet Mail Service (5.5.2650.21) id ; Mon, 31 Jul 2000 10:26:30 +1000 Message-ID: <216F15234CD5D311BBFA00484500A27701D295@FENCHURCH> From: Luke Mitchell To: questions@FreeBSD.ORG Subject: RE: What are the steps to start a binary at startup? Date: Mon, 31 Jul 2000 10:26:25 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > It almost seems like it's being killed by FreeBSD in some > sort of process > > cleanup. Is this possible? or likely? Any ideas? > > That's pretty much it. The problem I ran into was that something in > the startup sequence was sending HUP signals to my daemon to force it > to reread their it's files. Try ignoring HUP signals, and see if that > helps. > I tried running it with "nohup command &", but it still exits. Do you happen to know what the command arguments are? I've looked at man 1 nohup, but it is amazingly incomplete. The man page says that nohup can have an argument to also ignore SIGQUIT, but doesn't say what the arg is :-(. Thanks Luke Mitchell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message