![]() |
APMD-List: |
to APMD Home
|
Index:
[thread]
[date]
[subject]
[author]
From: Craig Markwardt <craigm@pcasun3.gsfc.nasa.gov> To : <apmd-list@worldvisions.ca> Date: Fri, 18 Jun 1999 15:03:00 -0400 (EDT) apm daemon, suspend/resume[ Discussion with PCMCIA maintainer David Hinds forwarded with permission. ] Craig Markwardt writes: > > Hi-- > > There have been some recent improvements to apmd, the user-land daemon > that does APM logging. apmd is now much more flexible about > performing user-specified actions before and after APM events ( see > http://www.worldvisions.ca/~apenwarr/apmd/ ). A small dispatcher > script called /etc/apmd_proxy is called for most APM events. > > The question we have been discussing now is, what default policy, if > any, should be applied. For example, the script currently calls > "cardmgr suspend" and "cardmgr resume" for suspend and resume events. > I am also aware that the PCMCIA kernel modules directly receive APM > events and respond to them. However, cards are hard suspended, > right(?) > > So, are there any peculiar interactions we should be worried about > during a suspend or resume? Is calling "cardmgr suspend" okay if the > kernel services have just been suspend or are about to be? > > Thanks for your input, > > Craig > > Index: [thread] [date] [subject] [author] |