Bug 1375882 - [SPEC] dbus-org.freedesktop.network1.service should go to systemd-networkd
Summary: [SPEC] dbus-org.freedesktop.network1.service should go to systemd-networkd
Keywords:
Status: CLOSED DUPLICATE of bug 1404444
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
: 1385522 (view as bug list)
Depends On:
Blocks: 74systemd
TreeView+ depends on / blocked
 
Reported: 2016-09-14 07:24 UTC by Petr Sklenar
Modified: 2017-02-20 12:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-20 12:49:40 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petr Sklenar 2016-09-14 07:24:28 UTC
Description of problem:
rpm -ql systemd shows many strange stuff
please investigate

Version-Release number of selected component (if applicable):
systemd-219-29.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1./usr/lib/systemd/system/dbus-org.freedesktop.network1.service is broken symlink

2.
rpm -qf /etc/systemd/system/runlevel5.target
systemd-219-29.el7.x86_64
ll /etc/systemd/system/runlevel5.target
ls: cannot access /etc/systemd/system/runlevel5.target: No such file or directory

and more:
/etc/machine-info: cannot open (No such file or directory)
/etc/systemd/system/runlevel2.target: cannot open (No such file or directory)
/etc/systemd/system/runlevel3.target: cannot open (No such file or directory)
/etc/systemd/system/runlevel4.target: cannot open (No such file or directory)
/etc/systemd/system/runlevel5.target: cannot open (No such file or directory)
/var/lib/systemd/backlight: cannot open (No such file or directory)
/var/lib/systemd/clock: cannot open (No such file or directory)
/var/lib/systemd/rfkill: cannot open (No such file or directory)
/var/log/journal: cannot open (No such file or directory)


Actual results:
broken symlink
there are files in the list but not on disk

Expected results:


Additional info:

for i in `rpm -ql systemd`; do file $i;done

search for broken/cannot ^

Comment 1 Lukáš Nykrýn 2016-09-14 08:48:11 UTC
Besides the dbus-org.freedesktop.network1.service symlink everything else is fine. Those files are marked as %ghost so it means that they are not packed inside the rpm, but they can exist on the machine. For example /var/log/journal will be created when user enables persistent logging.

Comment 2 Lukáš Nykrýn 2016-10-17 09:13:05 UTC
*** Bug 1385522 has been marked as a duplicate of this bug. ***

Comment 3 Lukáš Nykrýn 2017-02-20 12:49:40 UTC

*** This bug has been marked as a duplicate of bug 1404444 ***


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