From owner-freebsd-stable Thu Jul 20 12:59:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id B3E4337B5C7 for ; Thu, 20 Jul 2000 12:59:53 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from marlowe (Marlowe.campbell-mithun.com [192.159.32.184]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id PAA05465 for ; Thu, 20 Jul 2000 15:00:44 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <004d01bff285$21f21a70$b8209fc0@campbellmithun.com> From: "Shawn Barnhart" To: Subject: Does su have a builtin nohup? Date: Thu, 20 Jul 2000 15:00:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 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. Processes that generate lots of output also seem to generate lots of CPU usage running in this "background" mode. You can see this demonstrated by doing: $ su [-l] # while true; do date >> testing.txt; sleep 2; done (disconnect session) (on some other session on the same box) $ tail -f testing.txt Thu Jul 20 14:47:00 CDT 2000 Thu Jul 20 14:47:02 CDT 2000 Thu Jul 20 14:47:04 CDT 2000 (...continues until killed) Is this the way that it's supposed to work, or is this an its-not-a-bug-its-a-feature? -- swb@grasslake.net Hard work often pays off after time, but laziness always pays off now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message