From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2410 Path: news.gmane.org!.POSTED!not-for-mail From: Alex Efros Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Log rotation issue with runit Date: Tue, 25 Dec 2018 16:57:55 +0200 Organization: https://powerman.name/ Message-ID: <20181225145755.GF29946@home.lan> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1545749751 19973 195.159.176.226 (25 Dec 2018 14:55:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 25 Dec 2018 14:55:51 +0000 (UTC) User-Agent: Mutt/1.10.1 (2018-07-13) To: supervision@list.skarnet.org Original-X-From: supervision-return-2000-gcsg-supervision=m.gmane.org@list.skarnet.org Tue Dec 25 15:55:47 2018 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1gbo7W-00056F-9W for gcsg-supervision@m.gmane.org; Tue, 25 Dec 2018 15:55:46 +0100 Original-Received: (qmail 6052 invoked by uid 89); 25 Dec 2018 14:58:23 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 6045 invoked from network); 25 Dec 2018 14:58:23 -0000 Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2410 Archived-At: Hi! On Tue, Dec 25, 2018 at 01:39:17PM +0000, 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] https://bugs.debian.org/916230 .u files are created after svlogd crash (actually, when svlogd starts again after crash). I don't think I've ever seen actual crash of svlogd, so usually it means system was rebooted because of kernel OOPS or pressing reset button or power loss or someone has killed svlogd with SIGKILL. I believe this isn't a bug, but this behaviour isn't documented in svlogd man page. To me it looks useful to be able to detect such crash-reboots and what happens just before by looking for/in .u files. -- WBR, Alex.