Bug 4582 - limit command in /etc/csh.cshrc stops ~/.cshrc being read
limit command in /etc/csh.cshrc stops ~/.cshrc being read
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: setup (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-18 04:46 EDT by jason
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-20 18:31:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jason 1999-08-18 04:46:10 EDT
On some machines --- probably those with less memory
and/or swap --- the line

   limit coredumpsize 1000000

in /etc/csh.cshrc returns an error code and causes the
TCSH and CSH shells to stop processing their configuration
files. Among other things, this means that users .cshrc
or .tcshrc files are not read.

Replacing this line by

   limit coredumpsize unlimited

fixes the problem.

This seems to be related to bug 4071.
Comment 1 Jeff Johnson 1999-08-20 18:31:59 EDT
Fixed in setup-2.0.4-1.
Comment 2 Jeff Johnson 1999-08-20 18:32:59 EDT
*** Bug 4071 has been marked as a duplicate of this bug. ***

When ksh is used as the login shell and tcsh is invoked
sometime thereafter within a shell or terminal this error
message appears:

limit: coredumpsize: Can't set limit

This does not occur when you change shell in a terminal to
ksh and then to tcsh - only when ksh is the login shell.

This has existed at least since 5.0

Cheers,
Dan

------- Additional Comments From dkl@redhat.com  07/16/99 14:09 -------
I have verified that this does occur as reported on a standard 6.0
install. It is being assigned to a developer for further review.

Note You need to log in before you can comment on or make changes to this bug.