@hugbug, forum is back up so paste mail here, I know your checking on this.
Just did some extra testing because I think nzbget was not picking up (new) nzb's.
I changed the "NzbDirFileAge=60" in nzbget.conf to "20" and I think you are right, the scan function is working fine.
One thing I noticed is that when starting the daemon it sometimes picks up nzb's directly, and sometimes not.
It waits, in case not picking up directly, until "NzbDirInterval=60" time expires.
Because in my case this timer is set to "31536000" it waits for a long time.
(In fact it now starts when the Scan cron job kicks in.)
I use this "NzbDirInterval=31536000" trick value to pick up nzb's directly via stopping and starting the daemon by using the webinterface.
(Sometimes I don't want to wait for the Scan cron job.)
Maybe this can be fixed?
One "work-around" can be to make the Scan command available inside the webinterface?
To help you fix the problem I noticed in Top that, when starting the daemon, is see:
- 7x line: /ffp/bin/nzbget -D -c /ffp/etc/nzbget.conf (It picks up nzb's directly.)
- 5x line: /ffp/bin/nzbget -D -c /ffp/etc/nzbget.conf (It does NOT pick up nzb's directly.)
Tested with different values in "NzbDirInterval" and this doesn't change behaviour.