← Back to team overview

touch-packages team mailing list archive

[Bug 1428540] [NEW] tmpfiles.d order not respected any more, breaks rsyslog

 

Public bug reported:

With latest systemd we now get wrong permissions on /var/log when
rsyslog is installed:

drwxr-xr-x 1 root syslog 772 Mär  5 09:20 /var/log

It's supposed to be 0775, we install /usr/lib/tmpfiles.d/00rsyslog.conf
for that. As per documentation, the first match should win.

This is simple to reproduce:

$ cat test.conf
d /var/log 0775 root syslog -
d /var/log 0755 - - -

$ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create test.conf
[/home/martin/test.conf:2] Duplicate line for path "/var/log", ignoring.
Running create action for entry d /var/log
Found existing directory "/var/log".
chmod "/var/log" to mode 775
/var/log created successfully.
Running remove action for entry d /var/log
Running create action for entry d /var/log
Found existing directory "/var/log".
chmod "/var/log" to mode 755
/var/log created successfully.
Running remove action for entry d /var/log

So it doesn't recognize that it already has a match, and applies the
second rule anyway.

** Affects: systemd (Ubuntu)
     Importance: High
     Assignee: Martin Pitt (pitti)
         Status: In Progress

** Description changed:

  With latest systemd we now get wrong permissions on /var/log when
  rsyslog is installed:
  
  drwxr-xr-x 1 root syslog 772 Mär  5 09:20 /var/log
  
  It's supposed to be 0775, we install /usr/lib/tmpfiles.d/00rsyslog.conf
  for that. As per documentation, the first match should win.
  
  This is simple to reproduce:
  
- $ cat test.conf 
+ $ cat test.conf
  d /var/log 0775 root syslog -
  d /var/log 0755 - - -
- $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev test.conf
+ 
+ $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create test.conf
  [/home/martin/test.conf:2] Duplicate line for path "/var/log", ignoring.
  Running create action for entry d /var/log
  Found existing directory "/var/log".
  chmod "/var/log" to mode 775
  /var/log created successfully.
  Running remove action for entry d /var/log
  Running create action for entry d /var/log
  Found existing directory "/var/log".
  chmod "/var/log" to mode 755
  /var/log created successfully.
  Running remove action for entry d /var/log
  
  So it doesn't recognize that it already has a match, and applies the
  second rule anyway.

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- tmpfiles.d order not respected any more
+ tmpfiles.d order not respected any more, breaks rsyslog

** Changed in: systemd (Ubuntu)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1428540

Title:
  tmpfiles.d order not respected any more, breaks rsyslog

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  With latest systemd we now get wrong permissions on /var/log when
  rsyslog is installed:

  drwxr-xr-x 1 root syslog 772 Mär  5 09:20 /var/log

  It's supposed to be 0775, we install
  /usr/lib/tmpfiles.d/00rsyslog.conf for that. As per documentation, the
  first match should win.

  This is simple to reproduce:

  $ cat test.conf
  d /var/log 0775 root syslog -
  d /var/log 0755 - - -

  $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create test.conf
  [/home/martin/test.conf:2] Duplicate line for path "/var/log", ignoring.
  Running create action for entry d /var/log
  Found existing directory "/var/log".
  chmod "/var/log" to mode 775
  /var/log created successfully.
  Running remove action for entry d /var/log
  Running create action for entry d /var/log
  Found existing directory "/var/log".
  chmod "/var/log" to mode 755
  /var/log created successfully.
  Running remove action for entry d /var/log

  So it doesn't recognize that it already has a match, and applies the
  second rule anyway.

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


Follow ups

References