Bug 951956 - F18: stll not a systemd-unit
Summary: F18: stll not a systemd-unit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: preload
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-14 19:20 UTC by Harald Reindl
Modified: 2016-02-01 01:58 UTC (History)
1 user (show)

Fixed In Version: preload-0.6.4-9.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-02 06:32:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Harald Reindl 2013-04-14 19:20:51 UTC
[root@rh:~]$ rpm -q --file /etc/rc.d/init.d/preload
preload-0.6.4-5.fc18.x86_64

Fedora switched to systemd with F15
with each release there was "convert sysv-systemd" a feature
why are we still have packages with sysv-init instead systemd-units?

Comment 1 Harald Reindl 2013-04-14 19:39:55 UTC
and no, it's not that hard work to write a systemd-unit

[root@srv-rhsoft:/var/lib/preload]$ cat /etc/systemd/system/preload.service
[Unit]
Description=Adaptive readahead daemon
After=kdm.service

[Service]
Type=forking
ExecStart=/usr/sbin/preload --verbose 1
Restart=always
RestartSec=1
Nice=19
IOSchedulingClass=3

[Install]
WantedBy=multi-user.target

Comment 2 Fedora Admin XMLRPC Client 2013-08-05 18:11:05 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Jaromír Cápík 2013-09-19 16:40:41 UTC
A strange thing is, that I got the following error with SELinux/enforcing mode:
# service preload start
Redirecting to /bin/systemctl start  preload.service
Failed to issue method call: Access denied

The problem disappeared after calling the following:
# systemctl --system daemon-reload

Comment 4 Fedora Update System 2013-09-19 17:06:12 UTC
preload-0.6.4-9.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/preload-0.6.4-9.fc20

Comment 5 Harald Reindl 2013-09-19 17:18:17 UTC
the above is completly off-topic
the package doe snot contain any systend-unit - period

well, my machines have, see below - because i am tired
of running behind stupid maintainers not doing their job
and since F19 is the *fifth* release with systemd such
bugreports are laughable

[harry@srv-rhsoft:~]$ rpm -q --filesbypkg preload
preload                   /etc/logrotate.d/preload
preload                   /etc/preload.conf
preload                   /etc/rc.d/init.d/preload
preload                   /etc/sysconfig/preload
preload                   /usr/sbin/preload
preload                   /usr/share/doc/preload-0.6.4
preload                   /usr/share/doc/preload-0.6.4/AUTHORS
preload                   /usr/share/doc/preload-0.6.4/COPYING
preload                   /usr/share/doc/preload-0.6.4/ChangeLog
preload                   /usr/share/doc/preload-0.6.4/NEWS
preload                   /usr/share/doc/preload-0.6.4/README
preload                   /usr/share/doc/preload-0.6.4/THANKS
preload                   /usr/share/doc/preload-0.6.4/TODO
preload                   /usr/share/doc/preload-0.6.4/index.txt
preload                   /usr/share/doc/preload-0.6.4/proposal.txt
preload                   /usr/share/man/man8/preload.8.gz
preload                   /var/lib/preload
preload                   /var/lib/preload/preload.state
preload                   /var/log/preload.log
___________________________

[root@srv-rhsoft:~]$ cat /etc/systemd/system/preload.service
[Unit]
Description=Readahead daemon
After=kdm.service

[Service]
Type=simple
ExecStart=/usr/sbin/preload -f --verbose 1
Restart=always
RestartSec=1
Nice=19
IOSchedulingClass=3
ReadOnlyDirectories=/etc
ReadOnlyDirectories=/usr

[Install]
WantedBy=multi-user.target

Comment 6 Harald Reindl 2013-09-19 17:21:36 UTC
> The problem disappeared after calling the following:
> systemctl --system daemon-reload

this is not a problem, this is the *normal* behavior

look at other packages - they *all* call "systemctl --system daemon-reload"
over in the meantime years after *each* update because each update overwrites the systemd unit - thats why all the %post sections in RPM-SPEC's exists

Comment 7 Jaromír Cápík 2013-09-19 17:59:29 UTC
Dear Harald.

Maybe you haven't noticed, that I became the component owner a month ago. It would be nice of you to calm down and be nice to somebody who FINALLY wants to resolve this bug. I thought the new systemd macros are supposed to do the daemon reload automatically. That apparently didn't happen in my case.

Regards,
Jaromir.

Comment 8 Harald Reindl 2013-09-19 18:17:23 UTC
> would be nice of you to calm down and be nice to somebody who FINALLY

don't get me wrong, but after submitting and pinging bug over bug for a lot of packages since 2011 in case of systemd-units and hardening builds not following package-guidelines resulting in build nearly any for me relevant server package at my own fedora-packages in many cases does not interest me enough to get upset, so i can't calm down because of that

if Fedora is not able to keep a common level of packaging quality by too many too large steps wihin short time-frames Fedora should consider to calm down with it's heavy changes again and again and cleanup the still existing dirt in the distribution before create new

Comment 9 Fedora Update System 2013-09-19 18:35:19 UTC
Package preload-0.6.4-9.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing preload-0.6.4-9.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-17175/preload-0.6.4-9.fc20
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2013-10-02 06:32:09 UTC
preload-0.6.4-9.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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