Date: Fri, 23 Jul 2004 17:48:36 -0500 From: "Schmehl, Paul L" <pauls@utdallas.edu> Cc: <freebsd-rc@freebsd.org> Subject: RE: rc script won't start daemon on reboot Message-ID: <ADA47EFE15ACA74E8B702B6EF90D9139B63F03@UTDEVS08.campus.ad.utdallas.edu>
next in thread | raw e-mail | index | archive | help
> -----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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ADA47EFE15ACA74E8B702B6EF90D9139B63F03>