Why do so many people seem inclined to use screen when your typical Linux installation has 6(SIX!) VC's right at your fingertips. (ALT-F1 through ALT-F6) If that isn't enough and you don't want X, you can go all the way up to 24 just off the keyboard by spawning getty's or directly spawning processes on alternate VC's (another way to background it BTW). Besides, if you logout you loose the screen process so _that_ doesn't really answer his question. Using nohup (as previously mentioned and described) will do the job quite nicely, and I recall having some luck with simple backgrounding with stdout and stderr redirected. On Tue, 20 Nov 2001, Eric Stanley wrote: > I've found screen to be an extremely useful tool for things like this. > screen gives you the ability to start multiple virtual terminals > within a screen session. You can then detach from the entire screen > process, leaving it running. You can reattach to the session later > from elsewhere. It is even possible to detach the session without > being on the session. > > screen is a GNU tool, so if your distro doesn't have it, you can get > it from your local GNU mirror. > > HTH, > > Eric > > On Tue, Nov 20, 2001 at 09:34:51AM -0600, Simeon Johnston wrote: > > I have been wondering about something lately and can't figure it out. > > How do I background a process, say a kernel compile, so I don't have to > > sit there and watch it i.e. log in - start process - log out - log in > > later - find process done and everyones happy. > > > > How is this done? > > > > sim -- Daniel Taylor