MBOX-Line: From MRC at CAC.Washington.EDU  Fri Jun 30 13:46:32 2006
To: imap-protocol@u.washington.edu
From: Mark Crispin <MRC@CAC.Washington.EDU>
Date: Fri Jun  8 12:34:37 2018
Subject: [Imap-protocol] IMAP disconnection
In-Reply-To: <44A58633.6000601@gentoo.org>
References: <etPan.44a548f0.6bad5e90.d87@utopia>
	<Pine.OSX.4.64.0606300923160.408@pangtzu.panda.com>
	<kFysL5r4CM2misKgHbA2Fw.md5@libertango.oryx.com>
	<Pine.OSX.4.64.0606301005320.408@pangtzu.panda.com>
	<44A58633.6000601@gentoo.org>
Message-ID: <Pine.WNT.4.65.0606301343240.3552@Shimo-Tomobiki.panda.com>

On Fri, 30 Jun 2006, Jan Kundrt wrote:
> The server might have forked and the original process exited to avoid
> such behavior, but that would be rather dumb, of course :)

The process that is using the socket gets the kill.  So the server has to 
fork, the fork has to somehow stay in communication with its parent but 
not get hit by the kill, and yet still have control over the necessary 
resources to clean up...  And of course this has to be verified against 
the OS that does the kill.

All just so some poorly-written client can avoid obeying the IMAP 
protocol.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

