Warning / timeout creates unwanted S3 shutdown computer before finishing dloads.

[nzb_leecher]

2008-04-06 21:03:23,342::INFO::[decoder] Decoding
2008-04-06 21:03:23,342::INFO::[downloader] Thread [email protected]:119: fetchingblabla.nl
2008-04-06 21:03:23,342::INFO::[articlecache] Added to cache
2008-04-06 21:06:46,500::WARNING::[downloader] Thread [email protected]:119: timed out
2008-04-06 21:06:58,546::WARNING::[downloader] Thread [email protected]:119: timed out
2008-04-06 21:06:58,546::WARNING::[downloader] Thread [email protected]:119: timed out
2008-04-06 21:07:47,953::INFO::SABnzbd shutting down...
2008-04-06 21:07:48,500::INFO::[sabnzbd.misc] Dirscanner shutting down
2008-04-06 21:07:49,608::INFO::[downloader] Shutting down
2008-04-06 21:07:49,608::INFO::[assembler] Shutting down


My computer is on S3 mode, after no activity for 30 minutes, it shut down the computer is a sort of sleep mode. But it did that today even when it was not finished.
Normally this works ok and i have most of the time no problems, but because it just did it for the second time today, i looked in the log file and noticed something intresting.

At first i thought maybe SAB uses so less cpu, that the computer went to S3. So i wanted to ask for a settings that creates each 5 minutes a lot of cpu activity.
But this seems to be something else.

[nzb_leecher]

Another shutdown, i examened the log files, but time there isnt any written it just stopped writing to the log file.so no help form here, the message was about 21.15 while it dloaed for at least 30 minutes after that.
Could be becuase i looked in the file, maybe SAb saw it as locked and stopped writing.
btw i am now dloading but still anything isnt written to the log 

The first shutdown was not becuase of a timeout i see in the logfile, could be that the computer thought nothing was happening and closed the computer to S3 mode.