Bug 4071 - error message starting tcsh from ksh
error message starting tcsh from ksh
Product: Red Hat Linux
Classification: Retired
Component: pdksh (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Depends On:
  Show dependency treegraph
Reported: 1999-07-16 10:02 EDT by Dan Yocum
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-15 13:15:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dan Yocum 1999-07-16 10:02:31 EDT
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

Comment 1 David Lawrence 1999-07-16 14:09:59 EDT
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.
Comment 2 Jeff Johnson 1999-08-20 18:32:59 EDT
*** This bug has been marked as a duplicate of 4582 ***
Comment 3 Anonymous 1999-08-26 18:06:59 EDT
From an expert here at the Lab.  Enjoy.  Dan

The ulimit -c and limit coredumpsize values on trocious and bldlinux52
were both set to 1000000, but since these are in different units
(blocks and kbytes, respectively), they are inconsistent.  The
difference is only noticeable if your shell is sh/ksh/bash, and then
you switch to csh/tcsh, which gives an ugly error message, since
you're then attempting to double your quota, and it fails
to execute your .cshrc file.

The value in the /etc/profile files needs to be twice the value in the
/etc/csh.cshrc file, and I have made that change on trocious and

I believe on the latest 5.2 release, the value is being set in
/etc/bashrc, rather than /etc/profile, but it should be fixed wherever
it lives.

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