Sloan wrote:
Aaron Kulkis wrote:
Joe Sloan wrote:
Examples, please? What would be the security advantage of typing
"/opt/SunWzztop/bin/top" every time, instead of "top", with
/opt/SunWzztop/bin in the path?
[EMAIL PROTECTED]:~> which top
/usr/bin/top
[EMAIL PROTECTED]:~>
Why isn't top in /usr/bin where it belongs?
Our solaris boxes always had top and similar utilities in /opt. Maybe
it's different on solaris 10 (haven't checked), but historically, all
the old school unix vendors shipped pretty bare bones systems from a
usability point of view, and any useful extras tended to go either in
/opt or /usr/local.
We observe a few rules of thumb for the PATH of root - "." is verboten,
and world writable directories are out (actually any directory writable
by someone other than root is suspect). Other than those restrictions,
we prefer to use the path variable to make life less awkward and tedious.
And since top is trustworthy, just put a symbolic link in
/usr/bin to the top executable.
Admittedly, it's a patch up, but it's superior to playing
around with the $PATH variable(*) all the time
(*) for one, it doesn't help much for anyone who has a
currently running login with open shell windows, unless
they log off, or at the very least, shut all the shell
windows, and open up new ones.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
