Re:A cron pitfall that will probably snare you at least once...
by raldi on Monday June 27, 2011 @10:28AM
(#2701392)
My guess is they wanted to avoid running .dotfiles and #emacsbackup~ files and threw out the baby with the bathwater.
[ Parent
| on HN ]
Re:A cron pitfall that will probably snare you at least once...
by pyre on Monday June 27, 2011 @10:58AM
(#2701511)
Also '.bak' or '.old'
Re:A cron pitfall that will probably snare you at least once...
by qntm on Tuesday June 28, 2011 @08:59AM
(#2705182)
Isn't ".bak" a fairly logical file extension for a cron job intended to, e.g., perform backups?
Re:A cron pitfall that will probably snare you at least once...
by dexen on Monday June 27, 2011 @03:22PM
(#2702604)
Are #emacsbackup~ files executable by default? If not, that's a very weak reason.
(honestly I dunno; have never used EMACS yet)
Re:A cron pitfall that will probably snare you at least once...
by raldi on Monday June 27, 2011 @05:46PM
(#2703138)
Well, # is actually used for emacs autosave files (or something else regarding open buffers). Making ~ backups is indeed on by default.
Then again, if you're editing files in /etc/ as root and using emacs to do so, you kinda deserve what you get.
Re:A cron pitfall that will probably snare you at least once...
by dexen on Monday June 27, 2011 @05:53PM
(#2703150)
Wait, my intented question was, `do those backup files have the executable permission bits set'? Not `do they hold valid input for interpreter/CPU'.
In Slackware's startup scripts, there's a good bunch of
if [ -x SOME_FILE ]; then # if the file is executable, run it
./SOME_FILE start
fi
which makes it trivial to enable/disable various services by simply chmod +x SOME_FILE / chmod -x SOME_FILE. If EMACS' backup files were marked as not executable by the editor, that would be `case closed' for me, no need to pay extra attention to characters in file names.
Re:A cron pitfall that will probably snare you at least once...
by ars on Monday June 27, 2011 @11:14PM
(#2703905)
Yes, backup files have the executable bit set. They have the same bits as the real file.
They are in fact created by renaming the real file to the backup name, then saving the real file and copying the permissions.