Univention Bugzilla – Bug 32640
Inconsistent spelling of Cron vs. cron
Last modified: 2017-08-08 07:11:13 CEST
+++ This bug was initially created as a clone of Bug #30943 +++ FYI: If you read the documentation about "cron", you will see that the daemon calls itself "cron" and not "Cron". You will also find this reflected in <http://en.wikipedia.org/wiki/Cron> vs. <http://de.wikipedia.org/wiki/Cron>: Only because of the WikiCamalCaseRule the page-links use the upper-case-version, while on the pages itself they call themselves "cron" in English and "Cron" in German. (I know that WP is not authoritative.)
OTOH the README file calls it -- Vixie Cron V3.0 December 27, 1993 -- Also in 'man cron': cron - daemon to execute scheduled commands (Vixie Cron)
(In reply to Moritz Muehlenhoff from comment #1) > OTOH the README file calls it > > -- > Vixie Cron V3.0 > December 27, 1993 > -- > > Also in 'man cron': > > cron - daemon to execute scheduled commands (Vixie Cron) Because there it is Vixies "Cron", the *name* of that special implementation and the other is free to chose the writing of his liking. The generic service is still called "cron", in all-lower-case-letters. So either call it "Vixie Cron" (and never change or plan to change to any of the other implementations), or use the generic name, which is "cron". Here are 3 other implementations: <http://www.gnu.org/software/mcron/> <ftp://ftp.isc.org/isc/cron/cron_4.1.shar> <https://fedorahosted.org/cronie/> Either way, the spelling is inconsistent and should be harmonized.
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
This issue has been filed against UCS 3.2. UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.