Bug 1399602 - Don't run systemd-tmpfiles --create in service unit
Summary: Don't run systemd-tmpfiles --create in service unit
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nut
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 11:33 UTC by Juan Orti
Modified: 2018-05-29 11:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:30:05 UTC
Type: Bug


Attachments (Terms of Use)

Description Juan Orti 2016-11-29 11:33:13 UTC
Description of problem:
You should not run systemd-tmpfiles --create at service startup.

This line in the service units is not necessary:
ExecStartPre=-/usr/bin/systemd-tmpfiles --create /etc/tmpfiles.d/nut-client.conf

The temp directories are created at system boot by systemd-tmpfiles-setup.service. If you want the directory to be available right after installing the nut package, create and package it in the RPM as explained in the guidelines:

https://fedoraproject.org/wiki/Packaging:Tmpfiles.d

In addition to that, the tmpfiles configuration file has been changed in rawhide in bug #1394009


Version-Release number of selected component (if applicable):
nut-2.7.4-4.fc25.x86_64
nut-client-2.7.4-4.fc25.x86_64

Comment 1 Juan Orti 2017-05-24 06:10:42 UTC
This problem is still present in nut-client-2.7.4-7.fc26.x86_64

may 24 08:07:04 xenon systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller...
may 24 08:07:04 xenon systemd-tmpfiles[12970]: Failed to open '/etc/tmpfiles.d/nut-client.conf': No such file or directory
may 24 08:07:04 xenon systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller.

Comment 2 Fedora End Of Life 2018-05-03 08:17:47 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 11:30:05 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.