Arch Linux

When hplip is started for the first time after booting, the response is:

:: Starting hpiod: [DONE]
:: Starting hpssd: [FAIL]

At that point, /var/run shows hpiod.pid, hpiod.port, and hpssd.port only - no hpssd.pid. If hplip is restarted, the response is:

:: Stopping hpiod: [DONE]
:: Stopping hpssd: [BUSY]
rm: cannot remove `/var/run/hpssd.pid': No such file or directory
[DONE]
:: Starting hpiod: [DONE]
:: Starting hpssd: [DONE]

and /var/run now shows pids and ports for hpiod and hpssd. So far so good. ;)

However, I believe the use of `pidof -o %PPID python /usr/share/hplip/hpssd.py` in the init script is causing problems. If I run that pidof command on my system right now, two pids are displayed - 19467 19445, corresponding to this:

# ps ax | grep python
19445 ? S 0:00 python /usr/share/hplip/hpssd.py
19467 pts/0 S 0:00 python /home/tomk/adesklets/mailer-0.0.6/mailer.py

If I now stop hplip, both processes are killed:

# ps ax | grep python
19546 pts/2 S+ 0:00 grep python

and sure enough, my adesklet has disappeared. Based on my understanding of man pidof, I believe other running python processes would also be affected by this.