Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm not sure if this is new behavior, or just something I've never encountered, but I found it weird. I run Gentoo with Fluxbox, and have mrxvt as my terminal. When I type in a command with an & at the end,to make it a background process, it seems to work, but the process ends when I close the terminal. Should this be happening? I don't want it to happen, and there must be a way to work around it, so any help would be appreciated.
Yes it's normal. When you close a terminal, all child processes receive the HUP signal (Hand UP). The default behavior for most programs is to terminate when this signal is received, although it's possible for a programmer to write a program to ignore it.
There are a few ways you can prevent this.
1. prefix your command with nohup
2. run your programs in screen. This has the advantage that you can re-attach to them from another session if necessary.
I'm sure there are more too, but these two spring to mind.
I assume that's a typo? It is of course 'Hang UP', presumably a left over from dialup serial terminal days.
You can also use 'disown <job>' after a process has started, which is the equivalent of prefixing the command with 'nohup'. disown without arguments will disown all jobs (use bg first if the're stopped, or you'll need to do a kill -CONT <pid>).
However, as matthewg42 says, the best solution is screen, since then you can reattach later.
I assume that's a typo? It is of course 'Hang UP', presumably a left over from dialup serial terminal days.
Oops, yes. *blush*
Quote:
Originally Posted by soggycornflake
You can also use 'disown <job>' after a process has started, which is the equivalent of prefixing the command with 'nohup'. disown without arguments will disown all jobs (use bg first if the're stopped, or you'll need to do a kill -CONT <pid>).
However, as matthewg42 says, the best solution is screen, since then you can reattach later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
