From owner-freebsd-stable Thu Jul 20 13:37:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from dna.tsolab.org (dna.rockefeller.edu [129.85.40.125]) by hub.freebsd.org (Postfix) with ESMTP id EA78C37C16C for ; Thu, 20 Jul 2000 13:37:32 -0700 (PDT) (envelope-from dan@dna.tsolab.org) Received: (from dan@localhost) by dna.tsolab.org (8.10.1/8.10.1) id e6KKZ9V14881; Thu, 20 Jul 2000 16:35:09 -0400 From: "Dan Ts'o" Message-Id: <200007202035.e6KKZ9V14881@dna.tsolab.org> Subject: Re: Does su have a builtin nohup? To: swb@grasslake.net (Shawn Barnhart) Date: Thu, 20 Jul 2000 16:35:06 -0400 (EDT) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <004d01bff285$21f21a70$b8209fc0@campbellmithun.com> from "Shawn Barnhart" at Jul 20, 0 03:00:20 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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