| From: Brendan Halpin <brendan.halpin at ul.ie>
| Date: Tue, 17 Oct 2006 22:50:02 +0100
| I've got vague recollections from the distant past under Solaris
| or (less likely) Digital Unix, of having a setting (an environment
| variable set in the equivalent of .bashrc) that made all
| backgrounded jobs "nohup-ed".
| Am I imagining it? Is the a bash way of doing that? Is there any
| decent documentation on nohup? The man page is miserably
`stty -hup' perhaps?: no SIGHUP is sent on
last controlling tty close.
`trap "" 1' perhaps?: any SIGHUP is ignored by the
shell and all subsequent children.
neither is exactly the same as nohup(1) since
`nohup' also redirects stdout and/or stderr
(if they are the controlling(?) tty) to a file
besides ignoring SIGHUP; the above only either
preclude the usual case of SIGHUP or simply
ignore any SIGHUPs. and both of the above
effect more than backgrounded pipes.
my own vague recollection is the C-shell (csh(1))
had something like what is being asked about (I
don't recall what, I've always Hated `csh'), but
I cannot recall anything like that for any(?) of
the Bourne-ish shells.
Experienced (20+ yrs) kernel/software Eng: | Brian Foster Montpellier,
• Unix, embedded, &tc; • Linux; • doc; | blf at utvinternet.ie FRANCE
• IDL, automated testing, process, &tc. | Stop E$$o (ExxonMobile)!
Résumé (CV) http://www.blf.utvinternet.ie | http://www.stopesso.com
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!