I have multiple files with the same names that serve different purposes.
I need to differentiate them with extensions of `.sh`, `.cron` and
`.sysd` so the `locate` command returns sane results. If I have to use
`/etc/cron.d/myfile-cron` it spoils the file extension naming convention
with
Actually, /etc/cron.d/ is part of Linux Standards Base Core
Specification 4.0. http://refspecs.linux-foundation.org/LSB_4.0.0/LSB-
Core-generic/LSB-Core-generic/etc.html
Yes, .dpkg-* are ignored for a reason, but that also ignores the LSB FHS. If
you installed the lsb packages and expect a
It is actually documented further down in the man page and by the linux-
foundation.org that these files can have dots, in fact, multiple dots to
accomodate dns domain names.
** Changed in: cron (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a
Addendum: I wasn't aware that Fedora implemented this differently --
although it is not surprising as /etc/cron.d/ not part of any official
spec but rather an extension that was added by the individual distros.
I have this issue noted for now; perhaps something can be done via log
levels in
This is, in fact, documented. See:
http://manpages.ubuntu.com/manpages/maverick/en/man8/cron.8.html
Quoting (2nd paragraph):
Additionally, cron reads the files in /etc/cron.d [...] Files must conform to
the same naming convention as used by run-parts(8): they must consist solely
of upper- and
