Peter Vrabec wrote:
No, it not :-(. service rsyslog start will always start rsyslog, but we
need to start rsyslog only when sysklogd run before.
Well, then how about
%pre
if ( enabled syslog && running sysklog) then
touch /tmp/someflag
%post
if -f /tmp/someflag then
chkconfig --enable 35 rsyslog
as for if enabled -> chkconfig : chkconfig --list syslog | awk '{print
$5,$7}' | .....
if running: service syslog status | grep running
I don't see this as a huge problem, this is rawhide, it it expected to
kill your cat and eat your goldfish and from time to time it will even
upgrade some components (kernel etc.) requiring you a reboot.
Why kill fishes if a couple of bash lines would preserve them for your
piranha ?
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
