From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Craven Subject: Re: [PATCH] service: Honor #:log-file in make-forkexec-constructor. Date: Tue, 6 Sep 2016 22:02:00 +0200 Message-ID: References: <878tv6uk0v.fsf@gnu.org> <20160906123536.1321-1-david@craven.ch> <20160906211332.46c690db@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45060) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bhOBb-0002jP-Ej for guix-devel@gnu.org; Tue, 06 Sep 2016 17:45:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bhOBX-00025U-DW for guix-devel@gnu.org; Tue, 06 Sep 2016 17:45:42 -0400 Received: from mail-yw0-x233.google.com ([2607:f8b0:4002:c05::233]:33174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bhOBW-00024W-6E for guix-devel@gnu.org; Tue, 06 Sep 2016 17:45:39 -0400 Received: by mail-yw0-x233.google.com with SMTP id l8so69088744ywb.0 for ; Tue, 06 Sep 2016 14:45:37 -0700 (PDT) In-Reply-To: <20160906211332.46c690db@scratchpost.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: guix-devel >> Not syslog, but helps with debugging... > That definitely helps - however, in the long run, I think that using syslog is better. I agree, but someone has to write it... > Syslog does the splitting up in different files (or not) and onto different machines > (or not), filtering (or not), log rotation etc. So it makes sense to make services > use syslog instead of rolling-your-own filtering, splitting, networking etcetc 267843 > times. I don't intend to reimplement any of this. I just needed a way to dump stuff to a file instead of a tty. It's intended for usage during development of services, not for deployment. As Ludo mentioned it's not quite as simple as just redirecting stdout/sderr and needs some support in shepherd. Someone who actually runs services that require high availability will have to contribute better logging support ;) > That said the services should just use syslog on their own Many services expect stdout/stderr to be handled. I don't think that every service needs to reimplement basic logging functionality. systemd allows to set a services stdout and stderr to either journal/syslog/file/tty, so new services written for systemd expect this to be taken care of. > we could only guess when a new log message starts New lines are a pretty good guess.