Yeah, stepan, your fix would work just fine, but I'd much rather motion start as its own user. From a security standpoint, it just makes sense.
I customized the init script on my install for motion, and it more or less does what mouz's patches do, so it wouldn't be appropriate for SRU. In other words, motion can still start as its own user, but it has its own /var/run/motion directory to write to for its pid file so that it doesn't have to run as root (a little like how Tor is setup). The other thing that I did (which is different from mouz's patch) was that I created a separate config file for motion as a startup daemon in /etc/motion/motiond.conf. This way, individual users can still run motion normally (i.e. not as a daemon), and thus allaying any unintended side effects for that use case. I think that these kind of fixes are the most appropriate for the long term. -- Hardy upgrade - motion halts upgrade https://bugs.launchpad.net/bugs/198292 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
