Get help, report and discuss bugs.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 06 Feb 2009, 19:43
st_atime is modified even if someone reads the file. We should not concern about it at all.
phil-t wrote:
This does work, and as long as NzbFileAge is 1 or 2 seconds, it's not too bad a delay to the user.
It may be worth persuing a cleaner solution, as energy saving is one of the reasons people buy these embedded devices, and it's a hot topic on all the forums when the HDD's won't spin down etc..
Don't worry. NzbFileAge doesn't affect hdd spin. It's the option NzbFileInterval which affects it.
phil-t wrote:1. Change the remote 'scan' command behaviour as described above (i.e. if called remotely, ignore timestamp checks, assuming that the 'client' is in control of file creation etc before calling the scan command.
Probably the best solution. Will do it.
-
hugbug
- Developer & Admin
- Posts: 7645
- Joined: 09 Sep 2008, 11:58
- Location: Germany
Post
by hugbug » 10 Feb 2009, 18:22
phil-t wrote:1. Change the remote 'scan' command behaviour as described above (i.e. if called remotely, ignore timestamp checks, assuming that the 'client' is in control of file creation etc before calling the scan command.
Done in r285.
Who is online
Users browsing this forum: No registered users and 26 guests