Andreas Mohr wrote: > Package: pm-utils > Version: 1.2.6.1-3 > Severity: grave > Justification: most basic robustness principles violated, by a core system > package > > AFAICS even a single unfortunate failure during suspend usage can render > pm-suspend support terminally broken, with subsequent attempts always > exiting immediately, without any logging to occur (not even when trying to get > help by running pm-suspend --help or so) [I realize that hitting an > occupied lock probably shouldn't get logged, though]. > > Possible failure leading to pm-suspend breakage includes > - simple loss of power (notebook battery, wall socket) while suspended > - a crash during suspend \ both rather common > - a crash during resume / behaviour, sadly
In all those cases, you need to (re)boot your machine. If you are using tmpfs for /var/run, then /var/run/pm-utils/lock will automatically be clean, otherwise /etc/rcS.d/S??.d/mountall-bootclean.sh will clean up /var/run. So, I'm actually quite curious, how you managed to get such a stale lock file? Regarding your patch: I discussed that with my co-maintainer. His opinion is, that your proposed patch is rather a hack then a proper solution, as you would be unable to suspend for a whole day in case of stale lockfile. His suggestion was, to use /usr/bin/flock. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
