-
sdwdate-1.0.0-8 Stable
released this
2026-07-11 21:02:16 +02:00 | 0 commits to main since this releasesdwdate (LainOS Layer 02 port) ~ Changelog
1.0.0-8 ~ /etc/adjtime permission fix
Bug Fix
- Fixed
hwclock: cannot open /etc/adjtime: Permission denied, occurring afterhwclock --systohcsuccessfully ran (following the 1.0.0-5 fix) but couldn't read/write its clock-drift calibration file./etc/adjtimedefaults to0644, root-owned, with no group access. - Fix: added a
checkpathcall in the init script'sstart_pre()granting group access (root:sdwdate, mode0664). - An initial attempt at this fix (in 1.0.0-7, not separately released) used
checkpath -g sdwdate, an option that doesn't exist ~checkpathhas no-gflag. Corrected tocheckpath -f -m 0664 -o root:sdwdate /etc/adjtime, using-o user:groupinstead. - Verified end-to-end: forced a full service restart (guaranteeing a first-sync, which always uses the instant
/bin/date+hwclockpath regardless of correction size), confirmed the log showsInstantly setting the time, a successful/bin/date output, and noadjtimeerror ~hwclock --systohccompleted silently and successfully this time.
This is the third and final permission gap found through fresh-install testing in a clean KVM guest (after the RTC device access and
hwclockCAP_SYS_TIMEgrant in 1.0.0-5). All three were only caught by testing on a genuinely clean install rather than continuing to iterate on an already-patched development machine.
Downloads
- Fixed