[systemd-devel] pyload.service

[Colin Guthrie]

'Twas brillig, and Sw at g at 05/11/12 15:19 did gyre and gimble:
> Dear all,
> 
> As a Archlinux user which adopted systemd for the best, I moved my
> system to it. I follow the wiki to start pyLoad as a service creating
> the following file:
> /etc/systemd/system/pyload.service (sweetth being my user)

snip.

> PIDFile=/run/pyload/pyload.pid
> User=sweetth 

The problem here is likely that your user is not able to write in the
/run/pyload folder in order to write the pid file and systemd will start
the service, wait for the pidfile to appear and when it never shows up,
kill the service again after a timeout.

Simply create a tmpfiles.d snippet in /usr/lib/tmpfiles.d/pyload.conf
(or similar) with the following:

d /run/pyload 0755 sweetth - -


That should make the folder owned by your user and the service should
startup fine (might need a reboot or running systemd-tmpfiles --create
manually)

See man systemd-tmpfiles for more info.

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/