Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system Subject: Re: Sleep command Date: 11 Feb 2014 23:35:59 GMT Organization: People for the Ethical Treatment of Pirates Lines: 27 Message-ID: References: <100220142122043675%nospam@nospam.invalid> <100220142251476698%nospam@nospam.invalid> X-Trace: individual.net yZtpL5oAjH1YFV51piJ7jAFGgvRjCIjHThBlMByHtwlt/mwaz9 Cancel-Lock: sha1:ZFRuWLKQO/mEXIAx8FdsI3DCGAU= X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1Y%b|b-Y~()~\t,LZ3e up1/bO{=-) User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:56420 On 2014-02-11, dorayme wrote: > In article , > Jolly Roger wrote: > >> On 2014-02-11, dorayme wrote: >> > >> > I thought some logs might help, I have posted some. >> >> The log messages that are most important are the system and console log >> entries exactly when the machine wakes. Those messages will often tell >> you why the machine woke up. If you know the approximate time of the >> last wake event, you can scan the log to find entries around that time >> and post them here. > > I am happy to do this but why would the entries to do with why the > machine wakes up be relevant to why it takes 30 secs to sleep? Brain fart. Replace "wake" with "sleep" above. The point is the log entries will often mention what caused the wake/sleep event which, obviously, can be very helpful in determining the cause and appropriating a solution. ; ) -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR