John Goerzen <jgoer...@complete.org> wrote: Hi,
>> OK I've checked further, the error you got means the directory doesn't >> exist or isn't readable by mt-daapd. > > Which may have applied to the default directory they put in there, but > not to the one I tried to set it to. It also ignored any other config > file changes until I edited that with emacs. Once edited, it worked > perfectly -- scanned the files just fine. It should apply the changes on the fly, except maybe for the added directories; you may need to explicitely trigger a rescan. If you can reproduce the problem, try to get a log with mt-daapd -f -d 9 -D config,xml That may shed some light on what happened. I'm not too confident with the web interface for anything besides triggering a rescan or editing smart playlists. JB. -- Julien BLACHE <jbla...@debian.org> | Debian, because code matters more Debian & GNU/Linux Developer | <http://www.debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org