Summary: | fcron truncating jobs' lines in crontab file (all versions?) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gregg Casillo <gregg.casillo> |
Component: | [OLD] Core system | Assignee: | Cron Team <cron-bugs+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gregg Casillo
2005-10-03 11:29:47 UTC
Correction, I used a backslash to wrap the jobs on multiple lines. 3.0.0-r1? As for the log messages, the "(truncated)" just means the log message was truncated: In log.c: static char truncated[] = " (truncated)"; ... if (len >= MAX_MSG) strcpy(msg + (MAX_MSG - 1) - sizeof(truncated), truncated); Whoops, you're right about the log messages themselves being truncated. As for -r1, I created a custom ebuild in my overlay that allows fcron to be built without dependencies on ssmtp and mailbase; I detest mail servers. Not sure why it wasn't working before, but it's working again. record-v4l2.pl doesn't like it when the bitrate and peakbitrate are the same; I discovered this today while nosing around, and my jobs are running via cron again. So I'm happy. I'll close this bug. Sorry to trouble everyone over it. |