[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[50 character or so descriptive subject here (for reference)]
From: |
Alan Bain |
Subject: |
[50 character or so descriptive subject here (for reference)] |
Date: |
Wed, 31 Oct 2001 02:29:41 +0000 |
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu'
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -I.
-I/home/swt/doko/export/packages/bash/bash-2.03
-I/home/swt/doko/export/packages/bash/bash-2.03/lib -I/usr/include -g -O2
uname output: Linux pinochle 2.4.2 #1 Tue Feb 27 12:29:33 GMT 2001 i686 unknown
Machine Type: i386-pc-linux-gnu
Bash Version: 2.03
Patch Level: 0
Release Status: release
Description:
[Detailed description of the problem, suggestion, or complaint.]
Manual (info page) states on receipt of a SIGHUP bash
will send a SIGHUP to all jobs running or stopped. The
code actually seems to do this only if the session is
interactive. This is I think the POSIX behaviour
(but I can't find the standard at the moment) and
the manual contains the bug!
Repeat-By:
[Describe the sequence of events that causes the problem
to occur.]
Script run-long
#!/usr/local/bin/bash
run-long-job $1
~/run-long
At another session
ps -aux | grep run-long
PID 123
kill -HUP 123
Kills the bash instance but not the run-long-job child
which is what I would expect from the manual!
Fix:
[Description of how to fix the problem. If you don't know a
fix for the problem, don't include this section.]
Add information to manual!