Date: Mon, 15 Aug 2005 10:19:57 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Ken Gunderson <kgunders@teamcool.net> Cc: freebsd-amd64@freebsd.org Subject: Re: rc init path question Message-ID: <20050815171957.GC8859@odin.ac.hmc.edu> In-Reply-To: <20050815092434.282c53f5.kgunders@teamcool.net> References: <20050815092434.282c53f5.kgunders@teamcool.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--aT9PWwzfKXlsBJM1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 15, 2005 at 09:24:34AM -0600, Ken Gunderson wrote: > Greets: >=20 > Not strictly amd64 related but I'm not subsribed to questions so here > goes.... >=20 > Why is PATH set so restrictively (e.g. PATH=3D/sbin:/bin:/usr/sbin:/usr/ > bin) by rc init? Startup scripts in rc.d inherit this and seem to have > difficulties finding things upon boot whereas running the script > manually works fine since .cshrc has come into play by then. Or am I > totally missing something here.?? Predictability. Those directories should in general contain only system programs who's behavior should be what we expect. Adding other directories such as /usr/local/bin would complicate matters. This means you have to test slightly more carefully, but using full paths to commands is good practice in general, particularly for system startup scripts. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --aT9PWwzfKXlsBJM1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDAM68XY6L6fI4GtQRAjCGAJ9c1r7CZl17hMDuoUkXcLkCQk/+/ACgn6L4 A1CZ4jeahlm0p3cItYGtP+8= =fKm1 -----END PGP SIGNATURE----- --aT9PWwzfKXlsBJM1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050815171957.GC8859>