" Maynard) (03/30/89)
Bernie Hoffstadt (cutsys!cutter) had the answer. I had to add the line:
HISTFILE=/.history; export HISTFILE
to root's .profile.
Any idea why root would need that, while a normal user wouldn't?
--
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
uucp: uunet!nuchat! (eieio)| adequately be explained by stupidity.
hoptoad!academ!uhnix1!splut!jay +----------------------------------------
{killer,bellcore}!texbell! | "Less great!" "Tastes filling!"pcg@aber-cs.UUCP (Piercarlo Grandi) (04/01/89)
In article <2561@splut.UUCP> jay@splut.UUCP (Jay "you ignorant splut!" Maynard) writes:
Bernie Hoffstadt (cutsys!cutter) had the answer. I had to add the line:
HISTFILE=/.history; export HISTFILE
to root's .profile.
Any idea why root would need that, while a normal user wouldn't?
By the way, this is actually documented in the KSH manual. The reason is
fairly obvious: if you are not careful with your umask (e.g. it is 022 as
on many systems), the /.history file is readable by everybody, and this is
not something you really want. This applies also to other users, but root is
more sensitive, e.g. if root on one systems rlogins on another systems, and
puts the password on the command line etc...
Also, tipically root is a login that ought not to be used much.
(Well, I do use history on the root login on my machine, and make sure that
its permissions are u=rw,og= :->).
--
Piercarlo "Peter" Grandi | ARPA: pcg%cs.aber.ac.uk@nss.cs.ucl.ac.uk
Dept of CS, UCW Aberystwyth | UUCP: ...!mcvax!ukc!aber-cs!pcg
Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg@cs.aber.ac.uk