This fantastic. Indeed, this is completely undocumented. Running `grep -R 1000 .` on `apt-get-source cron` turns up: ./cron-3.0pl1/cron.h:#define MAX_

This fantastic. Indeed, this is completely undocumented. Running `grep -R 1000 .` on `apt-get-source cron` turns up: ./cron-3.0pl1/cron.h:#define MAX_COMMAND 1000 /* max length of internally generated cmd */ Further grepping for MAX_COMMAND gives you this gem: /* Everything up to the next \n or EOF is part of the command... * too bad we don't know in advance how long it will be, since we * need to malloc a string for it... so, we limit it to MAX_COMMAND. * XXX - should use realloc(). */ ch = get_string(cmd, MAX_COMMAND, file, "\n"); XXX - should use realloc(). Really?