[Bug 706565] Re: configs with dots in file name not working in /etc/cron.d

[WinEunuchs2Unix]

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 `/usr/local/bin/myfile.sh` and `/lib/systemd/system-
sleep/myfile.sysd`.

As per Ask Ubuntu question today:
https://askubuntu.com/questions/1020411/file-naming-conventions-for-
cron-and-systemd-extensions

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/706565

Title:
  configs with dots in file name not working in /etc/cron.d

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  I configured cron jobs with config file:
    /etc/cron.d/job.cron
  and it not working.
  I spend couple of hours to understand the problem.
  Fix is to rename file withowt dots in the name:
    /etc/cron.d/job
  is working.
  Renaming back to job.cron or other name with the dot in the name cause cron to not read this file.
  I just switched to Ubuntu Server from Fedora and it works before on those distributive.
  I can't find any error messages in syslog event with -L9 command line in cron daemon.
  I can't find any warning in man page or readme document about file names.

  I think there are 2 possible ways to fix this:
  1) put a WARNING about file names with dots (like "myjob.cron") in manpage;
  2) make cron working with those files as other distro do (ex. Fedora)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/706565/+subscriptions