Bug#569976: hrmm

[Mark Hedges <hedges@formdata.biz>]

Why do three `python hp-systray` procs get started anyway.
I guess each one tries a lock after the fork, instead of the
parent locking before the fork, and probably someone
expected that doesn't matter because they assumed the child
processes would get around to locking the file after the
parent made it to that point.  So the parent needs the lock
to succeed by validating the success of the file lock, but
the children do not, and ignore lockfile failure.  Except
the kernel might hand the child procs to other cpus, and
their execution could easily be faster, reaching the lock
routine first.

Mark