Maybe this theory doesn't make sense, because wouldn't
mod.lockInstance() block until it succeeds? And the fork
happens after the lock in /usr/bin/hp-systray. Where is the
code for lockInstance()?
Mark
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
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 m
2 matches
Mail list logo
