0000063: crond doesn't execute a crontab entry with no trailing EOL

BusyBox Bug and Patch Tracking

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000063

[BusyBox] Other

minor

always

01-26-05 14:31

09-01-05 03:24

Reporter

sbyrnand

View Status

public

Assigned To

BusyBox

Priority

normal

Resolution

fixed

Status

closed

Product Version

1.00

Summary

0000063: crond doesn't execute a crontab entry with no trailing EOL

Description

Spent about half an hour trying to figure out why my test crontab entry wasn't being executed and finally discovered that if I have a single line crontab entry with no end of line (LF ?) character following it, the entry is ignored.

I havn't tested it with multiple lines with the last line missing an end of line character, but it seems reasonable to assume the last entry wont get executed, and probably needs checking too.

Since many editors such as e3 won't put an end of line character at the end of a file unless you actually press enter, I can see a few people falling for this problem ;)

Additional Information

Attached Files

busybox-1.00-p03-crond.txt [^] (1,061 bytes) 08-12-05 03:10

Relationships

Notes
(0000407) psaksa 08-12-05 03:20	Attached patch - fixes whitespace issues during crontab parsing - fixes memory overflow issues with libbb trim function (by Vladimir N. Oleynik)

(0000479) landley 09-01-05 03:24	r11310

Issue History
Date Modified	Username	Field	Change
01-26-05 14:31	sbyrnand	New Issue
03-16-05 12:27	andersen	Assigned To	andersen => BusyBox
03-17-05 05:18	psaksa	Issue Monitored: psaksa
08-12-05 03:10	psaksa	File Added: busybox-1.00-p03-crond.txt
08-12-05 03:20	psaksa	Note Added: 0000407
08-13-05 11:03	swth	Issue Monitored: swth
09-01-05 03:24	landley	Status	assigned => closed
09-01-05 03:24	landley	Note Added: 0000479
09-01-05 03:24	landley	Resolution	open => fixed