ProtectHome setting in debian/rsyslog.service isn't understood by systemd
Bug #2051405 reported by
Anthony Harrington
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rsyslog (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Small bug introduced in commit e175f5c3668adc1
https:/
which changed the rsyslog.service line of
ProtectHome=yes to ProtectHome=
Systemd doesn't understand "readonly" https:/
and will mention in its journal:
systemd[1]: /lib/systemd/
Quickfix: just needs a hyphen on line 24 to read 'read-only'
Related branches
~xypron/ubuntu/+source/rsyslog:merge-lp2051405-noble-8.2312.0-3ubuntu3
Merged
into
ubuntu/+source/rsyslog:ubuntu/devel
at
revision 39fca86d8a54bc4013501123d1e796657008a619
- Nick Rosbrook (community): Approve
- Ubuntu Sponsors: Pending requested
- git-ubuntu import: Pending requested
-
Diff: 26 lines (+7/-1)2 files modifieddebian/changelog (+6/-0)
debian/rsyslog.service (+1/-1)
~xypron/ubuntu/+source/rsyslog:merge-lp2051405-noble-8.2312.0-3ubuntu3
Superseded
for merging
into
ubuntu/+source/rsyslog:debian/sid
- Nick Rosbrook (community): Needs Information
- Ubuntu Sponsors: Pending requested
- git-ubuntu import: Pending requested
-
Diff: 3344 lines (+2719/-43)38 files modifieddebian/00rsyslog.conf (+12/-0)
debian/50-default.conf (+48/-0)
debian/NEWS (+30/-0)
debian/README.apparmor (+132/-0)
debian/README.apparmor.rsyslog.d (+16/-0)
debian/apparmor/rsyslog-gnutls.apparmor (+3/-0)
debian/apparmor/rsyslog-mysql.apparmor (+20/-0)
debian/apparmor/rsyslog-openssl.apparmor (+3/-0)
debian/apparmor/rsyslog-pgsql.apparmor (+9/-0)
debian/changelog (+1878/-0)
debian/clean (+6/-0)
debian/control (+7/-2)
debian/dmesg.service (+13/-0)
debian/patches/omusrmsg-bugfix-potential-double-free-which-can-caus.patch (+69/-0)
debian/patches/plugins-FromHost-must-be-63-characters-long.patch (+44/-0)
debian/patches/series (+2/-0)
debian/reload-apparmor-profile (+14/-0)
debian/rsyslog-gnutls.install (+1/-0)
debian/rsyslog-mysql.install (+1/-0)
debian/rsyslog-openssl.install (+1/-0)
debian/rsyslog-pgsql.install (+1/-0)
debian/rsyslog.conf (+10/-26)
debian/rsyslog.dirs (+1/-0)
debian/rsyslog.docs (+1/-0)
debian/rsyslog.install (+6/-1)
debian/rsyslog.logcheck.ignore.server (+3/-0)
debian/rsyslog.postinst (+29/-0)
debian/rsyslog.postrm (+13/-0)
debian/rsyslog.service (+4/-8)
debian/rules (+8/-2)
debian/tests/apparmor-include-mechanism (+92/-0)
debian/tests/control (+20/-0)
debian/tests/logcheck (+13/-4)
debian/tests/simple-logger (+24/-0)
debian/tests/simple-mysql (+29/-0)
debian/tests/simple-pgsql (+25/-0)
debian/tests/utils (+76/-0)
debian/usr.sbin.rsyslogd (+55/-0)
Changed in rsyslog (Ubuntu): | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
Thanks Anthony for reporting the issue.
According to the systemd.exec.5 man-page:
ProtectHome= Takes a boolean argument or the special values "read-only" or "tmpfs".
Debian's rsyslog 8.2312.0-2 has rsyslog. service: 24:ProtectHome= yes
debian/
Ubuntu's rsyslog 8.2312.0-2ubuntu1 has rsyslog. service: 24:ProtectHome= readonly
debian/
Only Ubuntu Noble is affected.