motion fails to start because /var/run/motion is missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
motion (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: motion
I'll describe a fix first from which you may derive the problem: her is the fix:
install --group=motion --owner=motion -d /var/run/motion
once I did this then the init script would start motion.
Some other observations:
In the init script the "-b" flag to start-stop-daemon seems like the wrong thing to do, since motion can detach all by itself just fine and it is controlled in its config file. And actually using the config file setting causes problems with the -b flag here.
I could set the pidfile to /var/run/motion.pid but since motion runs as user motion this does not work.
This has actually been here since hardy, but I just upgraded to intrepid and see it still is here.
Changed in motion (Ubuntu): | |
status: | New → Confirmed |
The -b flag to start-stop-daemon really causes problems and should be removed. When motion believes it is running in the foreground it does not write a PID file