Right, what I'm seeing is that sm-notify drops the file there and then tries to notify remote hosts and fails because, for instance, its trying to mount the NFS filesystems before there is a net device. It most definitely should be cleaning this file up on this failure so we can try to run sm-notify again when the network is up.
My testing is almost complete and I think I've got it working reliably even when fsck's take a while.
Right, what I'm seeing is that sm-notify drops the file there and then tries to notify remote hosts and fails because, for instance, its trying to mount the NFS filesystems before there is a net device. It most definitely should be cleaning this file up on this failure so we can try to run sm-notify again when the network is up.
My testing is almost complete and I think I've got it working reliably even when fsck's take a while.