From owner-freebsd-stable Thu Jul 20 20:45:16 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 3ED6337B555 for ; Thu, 20 Jul 2000 20:45:09 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from k6 (k6.grasslake.net [192.168.2.1]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id WAA06137; Thu, 20 Jul 2000 22:45:53 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <001601bff2c6$06bcdbf0$0102a8c0@k6> From: "Shawn Barnhart" To: "Jared Chenkin" Cc: References: <200007210052.e6L0qm658557@voyager.bxscience.edu> Subject: Re: Date: Thu, 20 Jul 2000 22:44:51 -0500 Organization: Grasslake.Net MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Jared Chenkin" | Random question, but do you actually log out or do you just close the | ssh window? I notice that very often users on my system simply close | their telnet windows and the process does not die (namely the shell). | It became a real annoyance when telnetd(8) would start turning away | successful logins, complaining that all ttys were used up. Normally I log out like a good dog. The experience I was having was when my session was ended abruptly on the client end (machine lockup, loss of power or comms, etc). | I use screen(1) for things like this...build it in /usr/ports/misc/screen | Read the man page..its very useful and really cool :) | It allows you to drop screens and pick them up again later on by leaving | a named pipe in /tmp/screens/S-user. They're small so don't worry about | filling up teh root filesystem either :) I'm well accustomed to screen. Before I was rich and famous my "computer" was a VT320 with a modem and screen(1) was actually in my login script. Now that I'm fat, rich and lazy I find the GUI equivilent of screen, launching multiple ssh windows on my PC, to be a somewhat easier to deal with. So other than the 3 or 4 valid suggestion to use screen, does anyone have any concrete explanations as to why su keeps stuff running? Is it because the signal(s) jobs run in su'd environments get on session termination aren't privileged and they ignore them? Is this really considered a feature? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message