On 6 August 2010 18:14, Ted Unangst <ted.unan...@gmail.com> wrote: > On Fri, Aug 6, 2010 at 5:01 PM, Christiano F. Haesbaert > <haesba...@haesbaert.org> wrote: >> On 2 August 2010 00:47, Theo de Raadt <dera...@cvs.openbsd.org> wrote: >>> >>> Suspend and resumes are completely invisible, except that time makes >>> an uncomfortable jump forward. Processes are not made aware in any >>> way. There is no API to sense the transition (at this time). >>> >> >> What kind of approach would an API take, another socket type, like AF_ROUTE ? >> >> What about a new signal, if the default was to ignore, it wouldn't >> break signal semantics, although I agree that having a new signal may >> be too aggressive. >> >> I could benefit from such API, in mdns, if you know that you're about >> to lose connectivity you should issue a cache flush on your records, >> therefore it would be nice to receive an event such "about to >> suspend". >> >> I got my hands full right now but it seems like a nice thing to code in >> future. > > echo pkill -SIGOMG poniesd >> /etc/apm/suspend >
Sweet, disregard my previous post.
