Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#9831 - sysklogd doesn't support files > 2 gigs
Attached to Project:
Arch Linux
Opened by Dale Blount (dale) - Thursday, 13 March 2008, 20:26 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 15 March 2008, 02:59 GMT
Opened by Dale Blount (dale) - Thursday, 13 March 2008, 20:26 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 15 March 2008, 02:59 GMT
|
DetailsFrom sysklogd's README.1st:
* Large file support, i.e. support to write to log files that are larger than 2 GB is not part of syslogd, but a matter of the glibc emitting different system calls to the kernel interface. To support large files you'll have to compile syslogd with the compiler defines commented out in the main Makefile so that glibc adjusts the system calls. Possibility of lost security related logs raises the severity of this bug. |
This task depends upon
sed -i "s:-O3:${CFLAGS} -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE:" $startdir/src/$pkgname-$pkgver/Makefile || return 1
BTW, it seems that we need to use _LARGEFILE64_SOURCE instead of _LARGEFILE_SOURCE to fix this.
# ls -lh /var/log/mail.1
-rw-r--r-- 1 root root 2.9G 2008-03-14 00:02 /var/log/mail.1
It was stopping at 2G before my rebuild.