Date: Thu, 20 Jul 2000 16:35:06 -0400 (EDT) From: "Dan Ts'o" <dan@dna.tsolab.org> To: swb@grasslake.net (Shawn Barnhart) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Does su have a builtin nohup? Message-ID: <200007202035.e6KKZ9V14881@dna.tsolab.org> In-Reply-To: <004d01bff285$21f21a70$b8209fc0@campbellmithun.com> from "Shawn Barnhart" at Jul 20, 0 03:00:20 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> Does su have some kind of a built-in nohup option? If I su to root and > execute a command or shell script and then disconnect (ie, quit the terminal > software I'm running, which in my case is an ssh session) whatever I was > last running su'd as root continues to run until I manually kill it. I have noticed this too and have appreciated it as a "feature", though I consider it a bug. I am quite sure that is not the way original Unix worked. It may have to do with the way that process groups/privs are handling signals these days... Why it has been nice is that I quite often start up backup jobs remotely which can take several hours and from time to time the connection is severed, but the backup thankfully continued. I realize I could always use nohup, but... There should be a way to "reconnect" to disconnected jobs, much like in old TOPS-10, ie to reassociate controlling ttys to detached jobs. It is the I/O (stdin/stdout/stderr/ctty) analog of signals, parent/child, and job control. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007202035.e6KKZ9V14881>