Bug 87397

Summary: System crashes with hundreds of -bash spawned (1 user)
Product: [Retired] Red Hat Linux Reporter: Carl Eaton <cherme>
Component: bashAssignee: Tim Waugh <twaugh>
Status: CLOSED WORKSFORME QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: medium    
Version: 7.3CC: cherme
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: http://www.eatontown.net
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-03-29 01:25:02 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 Carl Eaton 2003-03-26 16:59:23 UTC
Description of problem:
System will lock up after few seconds of use.  Most notably
after logging in using ssh.  A "ps -ef" reveals hundreds of -bash 
spawned.  After that, "cat /proc/meminfo" shows no memory left.

Bug, s/w gone bad, or Virus?  

Version-Release number of selected component (if applicable):
7.3  All updates possible installed. (Have subscription)

How reproducible:
Very

Steps to Reproduce:
1.Login - especially with ssh
2."l" and "cd" some
3.check ps table and /proc/meminfo
    
Actual results:
System locks up after a few minutes.

Expected results:
Not lock up.  Not spawn hundreds of -bash processes.

Additional info:
It will still crash eventually but if I don't log in
it may run several hours before locking up.]

NOTE:
Mainly/Only use ssh, mail and web page.
Samba, telnet and ftp not even on the system.  I think my ipchains
is pretty strong.  Also a 6 hour memory test reveals no errors.

Comment 1 Tim Waugh 2003-03-26 17:04:42 UTC
This doesn't sound like a bash bug, but more like a misconfigured .bashrc in
your home directory or something.  What's in .bashrc?

Comment 2 Carl Eaton 2003-03-29 01:25:02 UTC
I commented EVERYTHING out in /home/(loginname)/.bashrc and
/etc/bashrc.  Can't readily discover what is sucking up the memory now
but it slowly erodes away slow enough I am getting my data
dumped to another system and then will scratch the disk.
Thanks