Description of problem: when running in a 32bit architecture (i386/i686 for example) cronolog won't be able to write to a file that is bigger than 2GB and will refuse to start if the log is that large as well, resulting in missing log data and reliability problems Version-Release number of selected component (if applicable): 1.6.2-4 How reproducible: always Steps to Reproduce: 1. configure an application to use cronolog to print (by piping to it) 2. let it run until the logs grows bigger than 2GB 3. restart application Actual results: application won't restart because cronolog would fail to start Expected results: application will start and keep writting to its log through cronolog Additional info: a patch is provided from upstream as shown in the URL, with the root cause being that LFS support wasn't enabled in cronolog latest released version
Created attachment 158573 [details] use O_LARGEFILE for basic LFS support in 32bit linux as currently being used in gentoo
Thanks for the patch, I've committed it and it will be included in release "5" as soon as it gets built and pushed out for F7. Sean