Date: Fri, 28 Jul 2000 18:04:05 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: questions@FreeBSD.ORG Subject: Re: What are the steps to start a binary at startup? Message-ID: <14722.4453.850059.202459@guru.mired.org> In-Reply-To: <bulk.94013.20000728025545@hub.freebsd.org> References: <bulk.94013.20000728025545@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi > Hopefully someone can help me with this, it's getting a bit frustrating. I've run into this kind of thing before, possibly my earlier experiences will help. > I can't get bpalogin to stay running if it's launched by rc ( ie. > /usr/local/etc/rc.d). The client starts but then exits without any errors. If you've got ports installing into /usr/local (which is the default), I'd recommend moving this to someplace else and setting local_startup in /etc/rc.conf to include that "someplace else". Personally, I put ports in /usr/opt, and reserve /usr/local for locally built tools that may not have an easy way to change that. > I've even tried running it in the foreground during startup to see if it > would exit, but it doesn't. Also tried running it with between "nohup" and > "&" with its 'remain in foreground' switch set. > > 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. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14722.4453.850059.202459>