News for hackers. Stuff that matters.
Re:A cron pitfall that will probably snare you at least once... by nbpoole on Monday June 27, 2011 @11:03AM (#2701527)
I found an older bug report for Debian that sheds a little light on why this behavior is useful: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308911

    I can understand not changing the behaviour wrt historical
    precedent: I have been told that people used to rely on the
    ignore-dot mechanism to disable things (e.g. mv foo foo.disabled).
At the end of the report, you can see they added the --regex flag to allow for user-defined filename validation.
Re:A cron pitfall that will probably snare you at least once... by raldi on Monday June 27, 2011 @11:27AM (#2701625)
They could at least log the skipping, by default.
Re:A cron pitfall that will probably snare you at least once... by ars on Monday June 27, 2011 @11:17PM (#2703909)
Considering how often these files are run that would make for quite a noisy logfile.
Re:A cron pitfall that will probably snare you at least once... by jsprinkles on Monday June 27, 2011 @11:54AM (#2701747)
Shhh! Don't make administrators' jobs easier! How else will we justify our insane salary and benefits?

Look at the bright side: this is a few days of debugging and difficult to explain to the people signing your check. Aren't you glad it's there now?

Re:A cron pitfall that will probably snare you at least once... by kaerast on Monday June 27, 2011 @01:57PM (#2702253)
A few days debugging? How could this possibly take any more than 5 minutes to work out on your own? If it takes a few days then maybe you are in the wrong job.
Re:A cron pitfall that will probably snare you at least once... by tvon on Monday June 27, 2011 @02:15PM (#2702358)
I think "a few days" was an intentional exaggeration.