--=-XxNlsoOqaHWSV1EEauEW Content-Type: text/plain Content-Transfer-Encoding: 7bit
On Sat, 2005-03-19 at 11:25 +0200, Oron Peled wrote: > On Friday 18 March 2005 12:00, shimi wrote: > > Well, I see it that way: > > > > If you kill a process, all the processes that were spawned by it are > > being killed as well [or supposed to be]. > > What you just described may exist in some other operating > system, but is definitely not Unix/Linux/Posix behavior. Funny, I could *swear* it happend to me in the past (like 7 years ago). (happend to me when I killed bash on a different connection, and my session died, although I was *in* a program). But I did work on many different systems back then, so, who knows :) Thanks for the heads up :) Still, why isn't that a good idea? You're leaving the program that sshd spawned (and it knows what it spawned, right?), which means you obviously want to stop ssh doing "his thing" for which you negotiated in the first place... I cannot see a reason to leave a stale session, which you really can't do anything with (like running 'fg' to take the process back to your control and communicate with it) ? Shimi -- --=-XxNlsoOqaHWSV1EEauEW Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.2.5"> </HEAD> <BODY> On Sat, 2005-03-19 at 11:25 +0200, Oron Peled wrote: <BLOCKQUOTE TYPE=CITE> <PRE> <FONT COLOR="#000000">On Friday 18 March 2005 12:00, shimi wrote:</FONT> <FONT COLOR="#000000">> Well, I see it that way:</FONT> <FONT COLOR="#000000">> </FONT> <FONT COLOR="#000000">> If you kill a process, all the processes that were spawned by it are</FONT> <FONT COLOR="#000000">> being killed as well [or supposed to be].</FONT> <FONT COLOR="#000000">What you just described may exist in some other operating</FONT> <FONT COLOR="#000000">system, but is definitely not Unix/Linux/Posix behavior.</FONT> </PRE> </BLOCKQUOTE> <BR> Funny, I could *swear* it happend to me in the past (like 7 years ago). (happend to me when I killed bash on a different connection, and my session died, although I was *in* a program). But I did work on many different systems back then, so, who knows :) Thanks for the heads up :)<BR> <BR> Still, why isn't that a good idea? You're leaving the program that sshd spawned (and it knows what it spawned, right?), which means you obviously want to stop ssh doing "his thing" for which you negotiated in the first place... I cannot see a reason to leave a stale session, which you really can't do anything with (like running 'fg' to take the process back to your control and communicate with it) ?<BR> <BR> Shimi<BR> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> <PRE> -- </PRE> </TD> </TR> </TABLE> </BODY> </HTML> --=-XxNlsoOqaHWSV1EEauEW-- ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
