Have been seeing a lot of this in mediatomb.log. Using v. 0.11.0-3 from Debian Lenny. Seems to occur when using inotify scanning. Wondered what it was all about?
Tks,
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried both, the acl and increasing how many files a user is allowed to watch. The error message goes away, but the artist still doesn't show up in the database. Also switching from Inotify to timed scan made no difference. There must be something about the files that mediatomb just doesn't like
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have been seeing a lot of this in mediatomb.log. Using v. 0.11.0-3 from Debian Lenny. Seems to occur when using inotify scanning. Wondered what it was all about?
Tks,
Brian
Sorry... sounds like a bug.
Problem persists according to https://forum.ubuntuusers.de/topic/inotify-fuer-minidlna-optimieren-max-user-inst (even after massive increase to fs.inotify.max_user_watches=1048576 in /etc/sysctl.conf).
ACLs required/expected to help?
I tried both, the acl and increasing how many files a user is allowed to watch. The error message goes away, but the artist still doesn't show up in the database. Also switching from Inotify to timed scan made no difference. There must be something about the files that mediatomb just doesn't like