On Sun, Oct 07, 2007 at 04:38:59PM +1000, Brian May wrote: > >>>>> "Kevin" == Kevin Mark <[EMAIL PROTECTED]> writes: > Kevin> How is this different from 'nohup' or screen? > > Answer is on the website, quoted: > > === cut === > > When Slashdot found out about detach, ScriptedReplay asked why one > would use detach, instead of nohup, which comes with the system. The > truth is that I didn't find nohup when searching for a command that > would run another command detached from the terminal. The reason is > that nohup doesn't really do that: > > nohup, as the name implies, makes your command ignore SIGHUP. That is, > unless you set a handler for it yourself, in which case you will still > receive the signal when the terminal exits. You can use normal shell > redirection and backgrounding on your process (although nohup will > automatically redirect standard output to nohup.out if you don't > redirect it). > > detach uses the setsid system call to detach the command from the > terminal.
$ apropos -s 1 setsid setsid (1) - run a program in a new session $ dpkg -S bin/setsid util-linux: /usr/bin/setsid If that's inadequate, let's enhance it instead of adding yet another program. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
