From owner-freebsd-questions Thu Jul 27 22: 7:53 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 8740037B63D for ; Thu, 27 Jul 2000 22:07:40 -0700 (PDT) (envelope-from luke@neither.apana.org.au) Received: (qmail 57264 invoked from network); 28 Jul 2000 05:07:32 -0000 Received: from unireg-gw.melbourne.austasia.net (HELO pc21.neither.apana.org.au) (203.23.160.199) by universalregistrations.com with SMTP; 28 Jul 2000 05:07:32 -0000 Received: (qmail 3626 invoked from network); 28 Jul 2000 05:07:05 -0000 Received: from unknown (HELO pc26.neither.apana.org.au) (192.168.20.26) by 192.168.20.25 with SMTP; 28 Jul 2000 05:07:05 -0000 Received: by FENCHURCH with Internet Mail Service (5.5.2650.21) id ; Fri, 28 Jul 2000 15:07:05 +1000 Message-ID: <216F15234CD5D311BBFA00484500A27701D291@FENCHURCH> From: Luke Mitchell To: "FreeBSD-Questions (E-mail)" Subject: What are the steps to start a binary at startup? Date: Fri, 28 Jul 2000 15:07:02 +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 Hi Hopefully someone can help me with this, it's getting a bit frustrating. I've recently subscribed to a cable modem service (Telstra Bigpond Advance in au). I've set up a box as a router (using FreeBSD 3.3, because that's the most current version of the cdroms I've got) and that all seems to work fine. The complication comes with the need to run and authentication client, to enable and hold open the connection. OK, so a cool guy as hacked a program which does this (bpalogin). It was written for linux environment, but compiles fine and runs happily from the command line. So what's the problem? 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. The startup script is simply; #!/bin/sh [ -x /usr/sbin/bpalogin ] && /usr/sbin/bpalogin -c /etc/bpalogin.conf && echo -n ' bpalogin' 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? Thanks in advance for any help Luke Mitchell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message