zzz reports `zzz: another instance of zzz is running` with mounted external hard drive because `/sys/power` cannot be locked
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- shell
- Domain
- operating-systems
Research direction
Start by locating where zzz acquires its lock on /sys/power and compare that path with the /var/lock/zzz.lock workaround shown in the report. Reproduce with the external HDD mounted and unmounted; done should mean zzz no longer reports another instance incorrectly and the existing suspend hook behavior remains intact.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C
- Stars
- 246
- Forks
- 67
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from void-linux/void-runit
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
void-linux/void-runit#141 ·
-
elogind service starts after sound device initialization, causing permission failuresPossibly taken @eholzbach claimed this 17 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
void-linux/void-runit#135 · 10 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
void-linux/void-runit#125 · 4 comments ·
-
key file and source not passed to keyscriptPossibly taken @shaohme claimed this 830 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
void-linux/void-runit#120 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
void-linux/void-runit#119 · 7 comments ·
All issues in void-linux/void-runit
Similar issues
-
backend
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BasedHardware/omi#20940 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kovidgoyal/kitty#10625 ·
Maintainers usually reply within 1 day
-
Feature Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day