Date: Thu, 20 Jul 2000 18:08:06 -0700 (PDT) From: Tom <tom@uniserve.com> To: Jared Chenkin <chenkinj@voyager.bxscience.edu> Cc: freebsd-stable@freebsd.org Subject: Re: your mail Message-ID: <Pine.BSF.4.05.10007201803180.18552-100000@shell.uniserve.ca> In-Reply-To: <200007210052.e6L0qm658557@voyager.bxscience.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Jul 2000, Jared Chenkin wrote: > In message <200007202035.e6KKZ9V14881@dna.tsolab.org>, "Dan Ts'o" writes: > >> 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. > > 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. Good Telnet clients should actually close the socket before quiting, and good OSes will automatically close any sockets left open when an application quits. Either of these would eliminate the problem you see. However, if a client crashes TCP keepalives should eventually timeout the socket on the server. There is a sysctl that forces TCP keepalives for all sockets that can be handy for services that don't necessarily use them. However, the telnetd service on FreeBSD uses keepalives by default. Tom Uniserve 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?Pine.BSF.4.05.10007201803180.18552-100000>