Talk:nohup

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

fetchmail

Isn't nohup in that fetchmail example superfluous since -d actually makes it a real daemon? 70.82.141.92

Yes, because fetchmail registers its own signal handler for SIGHUP – this is mentioned in the man page. nohup is only useful when the default signal handler would otherwise be used, terminating the process. — Lee J Haywood 21:15, 10 November 2005 (UTC)[reply]

Well, not only that; the main difference is that fetchmail -d already is a DAEMON, so it won't get any SIGHUP automatically because it'll detach from the controlling terminal and run in its own session (calls setsid(2)). This is different from how nohup(1) works. 70.82.141.92 02:35, 14 November 2005 (UTC)[reply]

weirdness

ANd here's some extra nohup weirdness. 70.82.141.92

dislocate

what is dislocate? the article mentions it, I cant find it on several linux distros... — Preceding unsigned comment added by 213.61.9.75 (talk) 11:26, 8 January 2013 (UTC)[reply]

Still didnt answer the question

As a user coming in here looking for info on nohup , The article fails to explain what happens when the user logs in again example

nohup wget a 1000 gb file &

When i log in is wget still spewing out information onto the telnet screen or does this program merely let the program run in the background and not be accesed again. —Preceding unsigned comment added by 86.46.165.229 (talk) 01:38, 11 June 2009 (UTC)[reply]

this article does not really answer your "log off / log in again" question because nohup knows nothing about logging in / logging off, this is way beyond of its very limited concern. Still, if you carefully read the article again, the explanations about redirections can give you a clue. But the best for you is to check the documentation of GNU Screen; a real, full-featured application as opposed to the minor nohup command Marchash (talk) 08:21, 11 June 2009 (UTC)[reply]

manpage link

The manpage link seems to be broken 190.138.237.70 (talk) 19:50, 4 January 2008 (UTC)[reply]

I replaced it with one that works. --Unixguy (talk) 19:01, 7 January 2008 (UTC)[reply]

Wikipedia NOT INFO

Thumperward, if you really think this page deserves this: ‹The template Manual is being considered for merging.›

then I am afraid you are basically going to have to tag most computer-related pages the same. Marchash (talk) 08:22, 11 June 2009 (UTC)[reply]

Double redirects

I had a program that I wanted to run with STDOUT to a file. Then I wanted to nohup it as well, keeping the program output separate. I sort of started off with:

nohup program >> program.out > /dev/null 2>&1

but this didnt work, so I settled for:

nohup `program >> program.out` > /dev/null 2>&1

which did work but was a bit of a mess, frankly. Anyone want to add these sort of conundrums to the article? — Preceding unsigned comment added by 82.134.237.45 (talk) 09:33, 18 March 2013 (UTC)[reply]

Relationship to systemd

Seems like there's some interesting things with systemd these days, after reading through Kill user session scope by default #3005 over on Github. Article might be able to benefit from some exploration of that - or maybe another article... Ben Creasy (talk) 08:09, 24 November 2016 (UTC)[reply]