Following up on my own report, the bug is caused by 03-gcc4.dpatch which
moves pidfile creation in front of the switch to user 'nobody', meaning
that the pidfile can actually be created in /var/run. Upon termination,
the daemon lacks capabilities to remove the pidfile, though. The most
elegant way
Package: pxe
Version: 1.4.2-3
Severity: grave
Justification: breaks system upgrades
The pxe daemon fails to start when there still is a stray pid file in
/var/run. Incidentially, it also fails to remove the pid file when
stopped. In combination, pxe is unusable after an upgrade until the old
pid f
2 matches
Mail list logo
