[hacknews] nohup

david@utzoo.UUCP (David Trueman) (06/22/84)

Nohup(1) now has a locking mechanism, to prevent a user from running
more than one background command at a time.
-- 
				David Trueman @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!david

david@utzoo.UUCP (David Trueman) (07/09/84)

Nohup(1) now traps interrupts, removing lock files if an interrupt is caught.
This deals with the situation where a person might invoke nohup without the
ampersand, then, realizing their error, hit interrupt.  Previously, the
process would die, but leave its lock files around.
-- 
				David Trueman @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!david

david@utzoo.UUCP (David Trueman) (04/18/85)

Some time ago, when too many people discovered background processing by
appending an ampersand to the command line, locking was added to nohup(1)
to prevent multiple simultaneous background processes by a single user.
Since ms(1) and format(1) now use batch(1) to queue print requests, this
need has largely disappeared, and the locking code has been removed from
nohup.

Now that's progress!
-- 
				David Trueman @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!david