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?
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?