Still present on Hardy-amd64 - I also had to fiddle out a workaround, a bit different, but same root cause:
motion (as daemon) runs as user=motion, group=motion which is correkt from point of security.
But this prohibits to place its PIDFILE in /var/run cause lack of permission.
Still present on Hardy-amd64 - I also had to fiddle out a workaround, a bit different, but same root cause:
motion (as daemon) runs as user=motion, group=motion which is correkt from point of security.
But this prohibits to place its PIDFILE in /var/run cause lack of permission.