This bug (487568) is related to #484570, where people argued against having world-readable configuration files. This was "fixed" in version 3.2.9-3 so the problem must have occured there already (against what the original report says).
The debian/motion.postinst file contains chmod 0600 /etc/motion/motion.conf. As the file is owned by root:root, the problem likely occurs when motion drops privilegies to motion:motion (but I haven't investigated further). One solution would possibly be to change to chmod 0640 and chgrp to motion. Another note about the postinst file, it creates /var/run/motion and sets up permissions and prepares stuff in the "create_pid_dir" function. Looks alot like someone didn't think about /var/run being on tmpfs and even if it's not, it's still wiped every reboot AFAIK?! The startup script of motion needs to handle this. -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
