On 27/09/16 13:09, to...@tuxteam.de wrote: > On Tue, Sep 27, 2016 at 10:55:52AM +0200, Tony van der Hoff wrote: >> On 26/09/16 17:04, to...@tuxteam.de wrote: >>> On Mon, Sep 26, 2016 at 04:38:01PM +0200, Tony van der Hoff wrote: >>>> On 26/09/16 16:03, to...@tuxteam.de wrote: >>>>> On Mon, Sep 26, 2016 at 12:54:49PM +0200, Erwan David wrote: >>>>> >>>>>> A possibility is that you have processes writing into deleted files. You >>>>>> can see them with lsof +L1 (as root) >>>>> > >> Thanks again to all who have helped with this. > >> After the overnight run, I'm now seeing this: > > [...] > > Bad Apache, bad :-) > > Seems this "cron job" is doing logrotate's job (or I am misunderstanding). > Well, I guess you're correct. It never occurred to me to use logrotate for this purpose. I imagined that was exclusively for the system packages. Evidently not!
However, it wouldn't work in this case. Various other applications rely on the names of the compressed files being in a particular format, which I can't easily achieve with logrotate. So, I'll stick with my original script but add "apachectl graceful" before fiddling with the files. The only snag seems to be that the script now has to run as root. Not a terrible deal. >> This setup has existed for a number of years unchanged, so what's caused >> it to start misbehaving? > I still don't understand what's changed; this server is running oldstable, so should only receive security updates. I guess it's just taken a long time to fill up the file space with deleted files. Ho hum! Thanks for your help. -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |