| Summary: | sysklogd ebuild does not compile in support for largefiles | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andrew Johnson <ajohnson> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | h3y |
| Priority: | High | ||
| Version: | 1.4_rc2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
sometimes largefile support means slower execution time how about using logrotate to solve getting that large files ? Sure, rotating more often is one way to solve the problem. But the thing is, syslogd crashes when it tries to write to a file over 2GB (at least in my case it did). It seems to me that sysklogd should not depend on logrotate in such a way that it will crash unless logrotate runs on time. This is why I consider this a bug that needs to be fixed. |
The apps-admin/sysklogd does not seem to force the use of the "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" flags during compilation and therefore the resulting syslog daemon cannot handle largefiles properly. Are we expecting folks to add this to their CFLAGS or should this be added to the ebuild? I would think most people would want their syslog daemon to handle files >2GB, as it is not at all uncommon for log files to get that large. I have noted that Apache does include these flags... I'm not sure why some ebuilds include them and some do not.