RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

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.

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.