ser2sock.pid?

[jplee3]

Anyone else having trouble not being able to get ser2sock to generate a pid in /var/run?

[jplee3]

To give some background, I just installed the AlarmDecoder image on my Raspi and everytime I boot/reboot it comes back with this error in /var/log/syslog:

Aug 29 13:52:48 alarmdecoder ser2sock[2191]: [‼] Error opening pid file /var/run/ser2sock.pid

If I `touch ser2sock.pid` and then chown it to pi:pi, things work as expected. But it looks like everything in /var/run is set to root:root by default and will revert back when rebooted as well.

[jplee3]

If I restart the service as the root user, there are no problems of course. It seems during boot/init though, the service seems to run as the pi user. Any way to change this?

[kevin]

As a workaround you can edit the /etc/init.d/ser2sock file and change the PID_FILE variable location to something writable by pi:pi on boot - thanks for pointing this out and it is now on our list of things to look at for the next image

[jplee3]

As a workaround you can edit the /etc/init.d/ser2sock file and change the PID_FILE variable location to something writable by pi:pi on boot - thanks for pointing this out and it is now on our list of things to look at for the next image

Ahh, thanks. I was pulling my hair out over that. I changed to /tmp and it seems to be OK now. Rebooting the Pi and *crossing fingers* - it should be OK though I think.