On Mon, Feb 15, 2010 at 05:57:48PM +0100, Michael Biebl wrote: > Andreas Mohr wrote: > > 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?
I cannot think of many reasons currently, but possibly due to using /bin/dash? (perhaps using the Debian bashisms script on the startup scripts would reveal something) I'll keep some notes and check it. > 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. Yes, indeed, in the light of flock it's a hack, I should somehow have managed to remember that there's flock :( (was somewhat in a hurry, and wanted to get it improved in any way, shape or form) > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? I'm sure that partly must be due to people unable to think of flock :) Andreas Mohr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100215181434.ga30...@rhlx01.hs-esslingen.de
