SABnzbd Forums

Weird, between 0.3.1RC1 and 0.3.1Final there were some changes that should prevent this particular problem.
I'll check it.

also the error that it can't connect to the nzb dirscan directory are flushing the usefull errors. I have the nzb directory on my desktop so if I turn on the nas/download server, it automaticly graps the nzb (I have not alway's my nas/download server up).

Grrr.
No: 0.3.1 has not completely been merged to the trunk.

Dexes: not being able to get to the dirscan dir should not be reported??
Seems to me that most people would be interested in that...
Ok, maybe one warning would be enough and not multiple.

shypike wrote: Grrr.
No: 0.3.1 has not completely been merged to the trunk.

Dexes: not being able to get to the dirscan dir should not be reported??
Seems to me that most people would be interested in that...
Ok, maybe one warning would be enough and not multiple.

for alot of people it is actually handy.. but not for me since the sab is on another pc than the nzb blackhole... but not a really good option to put it in as standard 

Like I suggested, I'll try to limit it to a single warning.
Remember the warning until the directory is visible.
When it disappears again: one new warning. etc.

that would be great!

Problem will be solved in 0.3.2