wasm-demo/demo/ermis-f/imap-protocol/cur/1600095133.22999.mbox:2,S

33 lines
1.4 KiB
Plaintext

MBOX-Line: From mrc at CAC.Washington.EDU Fri Jun 30 10:47:47 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: <rc1ASwIZw+RKCNvBsIFShQ.md5@libertango.oryx.com>
References: <etPan.44a548f0.6bad5e90.d87@utopia>
<kfeFnb6PW1GA+CfAeAs4lA.md5@libertango.oryx.com>
<Pine.OSX.4.64.0606301002220.408@pangtzu.panda.com>
<rc1ASwIZw+RKCNvBsIFShQ.md5@libertango.oryx.com>
Message-ID: <Pine.OSX.4.64.0606301045330.408@pangtzu.panda.com>
On Fri, 30 Jun 2006, Arnt Gulbrandsen wrote:
> Back when I looked at this, I didn't see find case where OS
> code seriously allowed applications to cancel the OS response to events like
> lid close - the choice was really between suspending the nice way or suffer a
> worse fate when the the nice processes are done.
It must have changed since you last looked at it. A certain well-known
financial application from a certain well-known vendor will (for reasons
that I can not fathom) cancel any attempt to sleep or hiberate; you are
required to exit the application first.
Also, laptop lid close is a software controllable event, and it can be set
in the OS to be "ignore completely".
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.