Bug 864656

Summary: Drop syslog dependency?
Product: [Fedora] Fedora Reporter: Ville Skyttä <ville.skytta>
Component: cronieAssignee: Marcela Mašláňová <mmaslano>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mmaslano, pertusus, tmraz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cronie-1.4.8-14.fc18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-15 08:55:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ville Skyttä 2012-10-09 21:09:52 UTC
With systemd providing syslog/journal, it seems that the dependency on syslog could/should be dropped from cronie. As it stands, cronie is the only thing on my system that prevents removal of rsyslog.

Comment 1 Marcela Mašláňová 2012-10-10 10:13:49 UTC
cronie requires syslog capability. I thought every logging tool will provide syslog in their provides.

Comment 2 Ville Skyttä 2012-10-14 13:56:35 UTC
(In reply to comment #1)
> cronie requires syslog capability.

Hm, really? That sounds unusual. AFAIK a lot of software will do syslog logging if syslog is available, but if not, they just don't do that but do work otherwise. Is cronie somehow different? Anyway, I'd say systemd and the syslog capability it provides is pretty much guaranteed to be around nowadays.

> I thought every logging tool will provide syslog in their provides.

I suppose that's pretty much an obsolete provision now, then.

Comment 3 Marcela Mašláňová 2012-10-15 08:55:13 UTC
You are very persuasive.