From owner-freebsd-rc@FreeBSD.ORG Fri Jul 23 22:48:36 2004 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA21816A4CE for ; Fri, 23 Jul 2004 22:48:36 +0000 (GMT) Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id A051843D2F for ; Fri, 23 Jul 2004 22:48:36 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from UTDEVS08.campus.ad.utdallas.edu (utdex08.utdallas.edu [129.110.70.103]) by smtp1.utdallas.edu (Postfix) with ESMTP id 5597A388D58 for ; Fri, 23 Jul 2004 17:48:36 -0500 (CDT) X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 23 Jul 2004 17:48:36 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: rc script won't start daemon on reboot Thread-Index: AcRvyjTwdZEZV44MRayoqnni637EhQBPJz7w From: "Schmehl, Paul L" Cc: Subject: RE: rc script won't start daemon on reboot X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to /etc/rc.d design and implementation. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2004 22:48:36 -0000 > -----Original Message----- > From: Oliver Eikemeier [mailto:eikemeier@fillmore-labs.com]=20 > Sent: Thursday, July 22, 2004 4:00 AM > To: Schmehl, Paul L > Cc: freebsd-rc@freebsd.org > Subject: Re: rc script won't start daemon on reboot > > > > bash-2.05b# ls -lsa /usr/local/bin/extractor 0 lrwxr-xr-x 1 root =20 > > wheel 34 Jul 12 15:34 /usr/local/bin/extractor ->=20 > > /usr/local/extractor/bin/extractor >=20 > This violates hier(7), but should not be the cause of any of=20 > your current problems. Perhaps Extractor depends on PATH or=20 > other environment variables that are not set during startup.=20 > Of course you can replace the symlink with a small shell=20 > script dumping the environment and wrapping the call to=20 > extractor with truss (or ktrace), but I would try debugging=20 > options to extractor first, or contact Symantec support. Btw,=20 > when extractor supports SIGHUP you can set `extra_commands=3D"reload"' > Thanks for the tip. I assumed that extra_commands goes in the script, not in rc.conf, right? I rm'd the symlink and cp'd the actual binary, but that didn't change anything. For now, I think I'll just let it go. The cron job ensures that the binary will start within 15 minutes of a reboot, and that's good enough for me. Maybe when I have more time in the future, I'll revisit it and try to figure out what the heck is going on. Your idea of the wrapper script is a good one. =20 Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/~pauls/=20