A fix has been prepared that recognizes too long commands and produces
an error message when attempting to create one, both via crontab(1) and
cron(8). Furthermore, this limit has been documented in the man pages.
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/826702
Title:
crontab cuts off file names at 100 characters
Status in “cron” package in Ubuntu:
Fix Committed
Bug description:
The crontab command silently cuts off file names after 100 characters.
This means that it won't work if you have a file with a path longer
than 100 characters, and want to feed it into crontab. Example:
$ crontab
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_this_will_be_cut_off
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345678:
No such file or directory
This is due to a MAX_FNAME constant set to 100 characters in cron.h. I
updated the code to use PATH_MAX instead. This will still cut off the paths,
but at least after a more reasonable number of characters.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/826702/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
