[Bug 2051405] Re: ProtectHome setting in debian/rsyslog.service isn't understood by systemd

[Heinrich Schuchardt]

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
debian/rsyslog.service:24:ProtectHome=yes

Ubuntu's rsyslog 8.2312.0-2ubuntu1 has
debian/rsyslog.service:24:ProtectHome=readonly

Only Ubuntu Noble is affected.

** Changed in: rsyslog (Ubuntu)
       Status: New => Confirmed

** Changed in: rsyslog (Ubuntu)
     Assignee: (unassigned) => Heinrich Schuchardt (xypron)

** Tags added: foundations-todo

** Tags added: fr-6404

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2051405

Title:
  ProtectHome setting in debian/rsyslog.service isn't understood by
  systemd

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Small bug introduced in commit e175f5c3668adc1c65f66efb61f70060569c9fe8
  https://git.launchpad.net/ubuntu/+source/rsyslog/commit/?id=e175f5c3668adc1c65f66efb61f70060569c9fe8

  which changed the rsyslog.service line of

  ProtectHome=yes to ProtectHome=readonly

  
  Systemd doesn't understand "readonly" https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html

  and will mention in its journal:

  systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse
  protect home value, ignoring: readonly

  Quickfix: just needs a hyphen on line 24 to read 'read-only'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2051405/+subscriptions