SABnzbd Forums

It would seem that you would want the server to resume/pause depending on the previous shutdown state.  So if this is the case, you need to have the status indicator on the QUEUE page reflect the correct current status.

Steps to recreate:

1) Add items to the queue
2) Download a few of them
3) Pause the server
4) Leave paused for a few minutes then shutdown the computer
5) Restart the machine
6) Open the sever webpage
7) Goto QUEUE page
eight) Status of the server is now running. <-- Should still be in the paused state.

Found on version 0.50 Final.

This is a tricky issue really.

I would much prefer someone accidentally be downloading, than go to their complete folder expecting content, then find their queue was paused all along.

If you must start with sabnzbd paused all the time pass it the command line parameter --pause

I guess we will have to see what everyone else thinks.

"see what everyone else thinks."

From someone who has a quota I definitely 2nd this. I can burn through a month of downloads in only a few hours, so one mistake and I'll be unhappy for the rest of the month. I watch sabnzbd like a hawk, but I do already use a lot of schedules to make sure it starts in the off state at peak times...

hmmm... would just setting *one* schedule to say "pause" at 00:00 daily mean that it would on start up read the schedule list, and because it should be paused, being the only schedule, it will??? always...
edit:
so for always unpaused- no change
always paused- set a scheduled to pause
remember last state- needs coding to go into setup file?