BUG: Ubuntu Gutsy 3.2.9 Deb - motion.pid directory and permissions error
Motion is installed on Ubuntu 7.10 Gutsy Server i386 system by using most recent Motion 3.2.9 Deb for Ubuntu Gutsy. Package installed using gdebi to best satisfy dependencies. On this system I also installed package kubuntu-desktop, which provides the KDE environment. Instead of using update-rc.d to make Motion auto-start in runlevel2, I used System Settings / Advanced (tab) / System Services. There I check the Start During Boot option, and started the service by pressing the Start button. A dialog box comes up showing any messages generated during the start process. Motion starts but an error is seen stating that the directory /var/run/motion/ was not present to create the motion.pid file (this directory is specified in motion.conf). That directory does not exist. Creating the directory /var/run/motion (change permissions to motion:motion) works if you kill motion and restart it, but that new directory is deleted on a reboot and Motion does not start because it can't create the motion.pid file in a /var/run/motion directory. Modifying motion.conf to place motion.pid in /var/run still shows the same error in syslog on reboot because of no write permissions to the /var/run directory.
Solution: In the /etc/motion/motion.conf file provided, the comments say that option process_id_file is not defined by default. But, the option is NOT commented out. Commenting out the option seems to fix the problem. The default process_id_file option in the /etc/motion/motion.conf should probably be commented out by default.
Paste in your error messages, config settings, terminal window output etc in this text field.
| Motion version:
| ffmpeg version:
|| Ubuntu Server default
| Shared libraries:
| Server OS:
|| Ubuntu Server 7.10 Gutsy + Kubuntu-Desktop
- 10 Mar 2008
Ubuntu packages are based in debian testing , so Ubuntu should has already a 3.2.9-2 based in :
- 16 Mar 2008