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?
# ls -l /lib/init/boot* -rw-r--r-- 1 root root 4865 Jun 26 2009 /lib/init/bootclean.sh.no Any further questions? :-P Well, yes indeed, /var/run/ likely is supposed to be a bit more "volatile" than the remaining bunch of directories on the system, thus it can be kind of expected to get purged rather frequently. Any suggestions as to which cave to choose to crawl back into now? :) Still I think that now using flock as a replacement wasn't such a bad idea anyway. Thanks for your very timely processing of this report, Andreas Mohr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
