Bug 203235 - cron doesn't honour MAXLOGNAME
Summary: cron doesn't honour MAXLOGNAME
Status: Closed DUPLICATE of bug 212305
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.2-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2015-09-21 16:19 UTC by Charles Lecklider
Modified: 2016-12-20 21:37 UTC (History)
2 users (show)

See Also:


Attachments
patch (887 bytes, patch)
2015-09-21 16:25 UTC, Charles Lecklider
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Lecklider 2015-09-21 16:19:46 UTC

    
Comment 1 Charles Lecklider 2015-09-21 16:25:00 UTC
Created attachment 161233 [details]
patch
Comment 2 Charles Lecklider 2015-09-21 16:38:04 UTC
It appears that cron has always had its own idea of how long a username can be, it's just been exposed by [r243023].

crontab truncates the tab filename to the first 19 characters and cron complains about orphans.

The fix is trivial.
Comment 3 Baptiste Daroussin freebsd_committer freebsd_triage 2016-12-10 12:55:52 UTC
Has been fixed in r305269
Comment 4 Ed Maste freebsd_committer freebsd_triage 2016-12-20 21:37:49 UTC
I'm sorry that we missed your PR and patch. Marking as a duplicate of the PR referenced in the commit.

*** This bug has been marked as a duplicate of bug 212305 ***