[50 character or so descriptive subject here (for reference)]

[ronan]

Configuration Information [Automatically generated, do not change]:
Machine: alpha
OS: osf4.0d
Compiler: cc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='alpha' 
-DCONF_OSTYPE='osf4.0d' -DCONF_MACHTYPE='alpha-dec-osf4.0d' -DCONF_VENDOR='dec' 
-DSHELL  -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib -I/usr/local/include -g
uname output: OSF1 mail.kerna.ie V4.0 878 alpha
Machine Type: alpha-dec-osf4.0d

Bash Version: 2.05
Patch Level: 0
Release Status: release

Description:
        [Detailed description of the problem, suggestion, or complaint.]

        The company I work for owns 2 Alpha machines running Digital
        Unix.  bash is my login shell on both machines.  If I log
        in to either of them over the network, start another program, 
        then break the connection, bash starts computing furiously
        and using up all the free CPU time.  The "other program" 
        dies, however.  I've tested this with both cat and more as the 
        other programs.

        I've verified that this doesn't happen when I have /usr/bin/sh
        as my login shell.

        The errant bash process can be killed with SIGHUP.
        (I know this is the usual behaviour for bash, but I thought
        I should mention that bash is working in this respect.)

Repeat-By:
        [Describe the sequence of events that causes the problem
        to occur.]

        The problem occurs if I do the following:

        Log into a machine running this version of Digital Unix using
        ssh or telnet (where my login shell on the Digital Unix 
        machine is bash).  Run the command
        "more /etc/passwd".  Close the window in which the local ssh or
        telnet process is running, or kill the local ssh or telnet
        process.