The web logs from the apache web server shipped with BCO are located in
These files are not rotated nor cleaned periodically: it might lead (over a long period of time) to file system saturation since the file can grow indefinitely.
The standard FileSystemCleaner task will not be able to delete the file as it's not rotated and always modified in recent minutes.
The current workarounds are
- truncate the file manually, periodically (once every few months)
- create a logrotate entry so that the standard logrotate activities take care of that
It would be nice if the BCO install procedure created a logrotate entry (with the right CPIT_BASE value according to local deployment options)