Bug 156730 - Launching an application from terminal with & for own process is still killed when terminal closed
Summary: Launching an application from terminal with & for own process is still killed...
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: ConsoleApps (show other bugs)
Version: unspecified
Hardware: PC SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 21:03 UTC by David Wright
Modified: 2006-03-09 21:40 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Wright 2006-03-09 21:03:12 UTC
I picked this up in one of the forums, and thought, hmm, that worked for me, but have just tested it and it is true.

I seem to remember from the old Unix and VMS days, and I think possibly before in SUSE 9 series, that launching an application from a terminal window adding an ampersand (&) launched the application in its own process and if the terminal was closed, the application kept on running.

With 10.0 this doesn't work, E.g. launching "mozilla &" from a terminal window opens mozilla as it should, but closing the terminal window also closes any applications which were launched from the terminal...

Is this changed design from Unix (and do I remember it incorrectly that this used to work with SUSE 9?) or has something changed recently?
Comment 1 Andreas Schwab 2006-03-09 21:40:31 UTC
Not a bug, you need to use nohup.