Bug 1018049

Summary: csh login/non-login history configuration is incorrect
Product: Red Hat Enterprise Linux 6 Reporter: Pavel Raiskup <praiskup>
Component: tcshAssignee: Jaromír Končický <jkoncick>
Status: CLOSED NOTABUG QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: low Docs Contact:
Priority: low    
Version: 6.6CC: ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-11 05:52:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pavel Raiskup 2013-10-11 05:20:37 UTC 
a) If 'tcsh' is run as non-login shell, the '$history' value has greater value
   than the value in '$savehist', which is bad according to tcsh documentation.

b) If 'tcsh' is run as login shell, the '$savehist' does not have the keyword
   'merge' inside.  This may (quite unlikely, though) trim the ~/.history file.
Comment 1 Pavel Raiskup 2013-10-11 05:32:05 UTC 
I problem b) should be treat as high severity.  If user has set the default
shell to 'tcsh', the first starting and last shutdown tcsh instance is run as
login shell - thus, most likely, the history file is going to be truncated.
Comment 2 Pavel Raiskup 2013-10-11 05:42:25 UTC 
Ok, scratch the comment #1, that is not truth.  I had misconfigured local
settings.  But the a) case seems to be still issue, though with much lower
severity.
Comment 3 Pavel Raiskup 2013-10-11 05:52:49 UTC 
Looking it once again and even the a) case seems to be innocent to me (the
only thing what happens is that max(savehist, history) number of history
entries will be saved at shutdown).  Thus closing, sorry for noise.