Bug 4582
Summary: | limit command in /etc/csh.cshrc stops ~/.cshrc being read | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | jason |
Component: | setup | Assignee: | David Lawrence <dkl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | dyocum |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-08-20 22:31:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jason
1999-08-18 08:46:10 UTC
Fixed in setup-2.0.4-1. *** 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 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. |