I've been using sleepwatcher for some time to unmount my SD card before sleep and to set brightness on wake. However, it's come with a price - when sleepwatcher is running, there is at least a 10 second delay on wake where the system is completely unresponsive. No disk activity, but it still seems to be I/O blocked, as the GUI blocks on any action. On shutdown, everything again stalls for ten seconds or so, and in verbose mode a warning is finally printed to the effect that sleepwatcher did not respond to a SIGTERM signal. Now this is odd, since issuing a kill command works fine, and the source code explictly handles SIGTERM. If I remove sleepwatcher, all of this goes away. It's also unlikely that it's my scripts - my wake script just sets brightness (two lines of reggie_se), and my sleep script unmounts the SD rather forcefully (umount hardcoded to the volume name). Oh, and it's not my SSD - I'm on a 64GB RunCore, and everything *flies*, and anyway the problem vanishes when I'm not running sleepwatcher.
Has anyone else seen behavior like this, or are there any other suggestions? I don't want to give up sleepwatcher, but this is getting very old.
