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
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.
*** This bug has been marked as a duplicate of 4582 ***
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 bldlinux52. 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.