cronolog doesn't support files larger than 2GB
Bug #180745 reported by
Carlo Marcelo Arenas Belon
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cronolog (Debian) |
Fix Released
|
Unknown
|
|||
| cronolog (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: cronolog
problem is that cronolog doesn't open the log files using LFS and is therefore limited by the max size of an int in all 32 bit architectures.
this is a known problem in debian for several years as can be seen by :
http://
http://
and has been reported upstream and available from there with a proposed fix as can be seen in :
http://
to reproduce : in a 32bit architecture (like i386)
$ cat /dev/zero | cronolog log
$ echo $?
5
$ stat -c "%s" log
2147483647
it affects all versions of cronolog released
Revision history for this message
| Carlo Marcelo Arenas Belon (carenas) wrote | #1 |
| Changed in cronolog: | |
| status: | Unknown → New |
Revision history for this message
| Maxime Chatelle (xakz) wrote | #2 |
| Changed in cronolog (Debian): | |
| status: | New → Fix Released |
Revision history for this message
| Evan Peck (colors) wrote | #3 |
| Changed in cronolog (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Shahid (shahid-afraid111) wrote | #4 |
To post a comment you must log in.
after the maximum file log size has been reached :
$ cat /dev/zero | cronolog log
File size limit exceeded (core dumped)
$ echo $?
153