Bug 1734712 - service fail to start because systemd unit file issue
Summary: service fail to start because systemd unit file issue
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: apt-cacher-ng
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kenjiro Nakayama
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-31 09:52 UTC by Kai Fan
Modified: 2019-07-31 09:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Kai Fan 2019-07-31 09:52:33 UTC
Description of problem:

apt-cacher-ng service can’t start because of there’s no /var/run/apt-cacher-ng directory.

As the /var/run is a runtime dir, I have to add following line into [Service] Section to make it running.

    [Service]
    RuntimeDirectory=apt-cacher-ng


Version-Release number of selected component (if applicable):

3.1-4el7

How reproducible:

Just install and then try start the service.


Steps to Reproduce:
1. yum install apt-cacher-ng
2. systemctl start apt-cacher-ng
3. systemctl status apt-cacher-ng

Actual results:

apt-cacher-ng failed to start

Expected results:

apt-cacher-ng started as a systemd monitored service

Additional info:

man systemd.directrives
man systemd.exec


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