You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a setup with a 2TB Intenso HDD connected externally and when the disk is mounted, zzz will report
sudo zzz
zzz: another instance of zzz is running
Unmounting the disk through a /etc/zzz.d/suspend script has no effect because zzz never gets there, it fails to get the lock on /sys/power. Unmounting the disk prior to executing zzz allows the lock to be acquired.
Changing the script to
echo "yawn."
) 9>/var/lock/zzz.lock
always works and there are no issues. I also do not understand the very specific choice of /sys/power as a lock target.
The text was updated successfully, but these errors were encountered:
I have a setup with a 2TB Intenso HDD connected externally and when the disk is mounted,
zzz
will reportUnmounting the disk through a
/etc/zzz.d/suspend
script has no effect becausezzz
never gets there, it fails to get the lock on/sys/power
. Unmounting the disk prior to executingzzz
allows the lock to be acquired.Changing the script to
always works and there are no issues. I also do not understand the very specific choice of
/sys/power
as a lock target.The text was updated successfully, but these errors were encountered: