Bash does not respect nohup setting
Bug #723692 reported by
Kjell L.
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bash
Option huponexist is set to be off but bash still close background jobs. I remember before Maverick and maybe Lucid that background jobs did not close even if you close the terminal. So this is a regression.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bash 4.1-2ubuntu4
ProcVersionSign
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Feb 23 13:41:03 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: bash
To post a comment you must log in.
This is normal behavior that has never changed. When a terminal is closed, the kernel sends SIGHUP to all attached processes. It has nothing to do with bash. The usual method of allowing a program to run in the background after closing the terminal is to run it with the nohup program.
If you can get a backgrounded job to remain running after closing the terminal ( other than by using nohup ) on lucid, could you describe how?