From owner-freebsd-rc@FreeBSD.ORG Fri Jul 23 23:06:15 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 680ED16A4CE for ; Fri, 23 Jul 2004 23:06:15 +0000 (GMT) Received: from fillmore.dyndns.org (port-212-202-50-15.dynamic.qsc.de [212.202.50.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1566D43D2D for ; Fri, 23 Jul 2004 23:06:15 +0000 (GMT) (envelope-from eikemeier@fillmore-labs.com) Received: from dhcp-13.local ([172.16.0.13] helo=dhcp-11.local) by fillmore.dyndns.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.41 (FreeBSD)) id 1Bo97D-000KQd-4g; Sat, 24 Jul 2004 01:06:14 +0200 Date: Sat, 24 Jul 2004 01:07:13 +0200 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) To: "Schmehl, Paul L" From: Oliver Eikemeier In-Reply-To: Message-Id: <08B735A5-DCFD-11D8-BA2D-00039312D914@fillmore-labs.com> Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: freebsd-rc@freebsd.org 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 23:06:15 -0000 Schmehl, Paul L wrote: >> -----Original Message----- >> From: Oliver Eikemeier [mailto:eikemeier@fillmore-labs.com] >> 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 >>> wheel 34 Jul 12 15:34 /usr/local/bin/extractor -> >>> /usr/local/extractor/bin/extractor >> >> This violates hier(7), but should not be the cause of any of >> your current problems. Perhaps Extractor depends on PATH or >> other environment variables that are not set during startup. >> Of course you can replace the symlink with a small shell >> script dumping the environment and wrapping the call to >> extractor with truss (or ktrace), but I would try debugging >> options to extractor first, or contact Symantec support. Btw, >> when extractor supports SIGHUP you can set `extra_commands="reload"' >> > Thanks for the tip. I assumed that extra_commands goes in the script, > not in rc.conf, right? Jup, is is documented in rc.subr(8), although not easy to find. > 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. My first guess would be the environment, like PATH. Anyway, Symantec should care. Have you tried to contact them? Ah, and since you are concerned about security, have you tried portaudit? (Shameless hijack of this thread, please follow-up to freebsd-security@) -Oliver