Log rotation issue with runit

2018-12-25 Thread Dmitry Bogatov
Hello! I am Debian maintainer of `runit' supervision suite. Recently, I received bug report [^1] about stray .u logfiles. After some investigation I found code, that caused issue, but it seems that it was written with some purpose, yet I fail to understand that purpose. Author Gerrit Pape direc

Re: Log rotation issue with runit

2018-12-25 Thread Alex Efros
Hi! On Tue, Dec 25, 2018 at 01:39:17PM +, Dmitry Bogatov wrote: > Recently, I received bug report [^1] about stray .u logfiles. After > some investigation I found code, that caused issue, but it seems that it > was written with some purpose, yet I fail to understand that purpose. > > [^1] htt

Re: Log rotation issue with runit

2018-12-25 Thread Guillermo
El mar., 25 dic. 2018 a las 10:39, Dmitry Bogatov escribió: > > Hello! > > I am Debian maintainer of `runit' supervision suite. Recently, I > received bug report [^1] about stray .u logfiles. After some > investigation I found code, that caused issue, but it seems that it was > written with some pu

Re: Log rotation issue with runit

2018-12-25 Thread Guillermo
> […] Both .u and .s files are supposed to > be deleted when they are the oldest file in the logging directory, to > honor 'u' lines in 'config' files, […] Sorry, that should have read: to honor 'n' lines in 'config' files. G.

Re: Log rotation issue with runit

2018-12-25 Thread Alex Efros
Hi! I'm not sure is it good idea to include .u files in usual rotation process at all, and especially handle them just like .s files. If several crashes happens for some reason in a short period of time this will result in deletion of all log files except last (say) 10 .u files, which are usually

Re: Log rotation issue with runit

2018-12-25 Thread Steve Litt
On Tue, 25 Dec 2018 13:39:17 + Dmitry Bogatov wrote: > Hello! > > I am Debian maintainer of `runit' supervision suite. Recently, I > received bug report [^1] about stray .u logfiles. After some > investigation I found code, that caused issue, but it seems that it > was written with some purp