From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3306D138E20 for ; Thu, 20 Feb 2014 11:53:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 26DE2E0B48; Thu, 20 Feb 2014 11:53:25 +0000 (UTC) Received: from forward2l.mail.yandex.net (forward2l.mail.yandex.net [84.201.143.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C309FE0A0B for ; Thu, 20 Feb 2014 11:53:23 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward2l.mail.yandex.net (Yandex) with ESMTP id A547A1AC1092 for ; Thu, 20 Feb 2014 15:53:21 +0400 (MSK) Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id 4DF4CE40092 for ; Thu, 20 Feb 2014 15:53:21 +0400 (MSK) Received: from unknown (unknown [91.233.55.8]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id iDhyt9pnAZ-rKcC9VRD; Thu, 20 Feb 2014 15:53:21 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: 5d970847-7915-4c45-8c1c-99fc986b5594 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1392897201; bh=p5Q84z1y+S+gxWzVXU2K3AN+J+oqi8hlbL4jcrdTFIY=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=tjJmSQ7M0azjQvkDx6E05VNR0aBLXkizTS6u17c/mJgYUKF1DJLgNwfRX7QtvDOmd HlCT/djcnhXxFfp6lxvQfWyA49hbrpr2sO6ewcCx7lEaHFJ6cdKwKTxMZqNplmBENw LW+7UkvbiCNxGjptv2K4vSKh2BF9bU9jC7UkkOZA= Authentication-Results: smtp13.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5305ECB0.7060706@yandex.ru> Date: Thu, 20 Feb 2014 15:53:20 +0400 From: "Yuri K. Shatroff" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Debian just voted in systemd for default init system in jessie References: <53010A8E.2050909@googlemail.com> <53012691.6040503@googlemail.com> <5ea6afc66880871ddec1398bab1e1f17.squirrel@www.antarean.org> <31f183759cbab018caa5523ab4974175.squirrel@www.antarean.org> <5305C7E3.9030906@yandex.ru> <20140220113305.GB6784@sabayon.logifi> In-Reply-To: <20140220113305.GB6784@sabayon.logifi> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 937c3fa4-5546-44ec-9f36-3bc075b5ae7d X-Archives-Hash: 7c035d7d0cecf563ff245b98fdb553e5 20.02.2014 15:33, Nicolas Sebrecht пишет: > The 20/02/14, Yuri K. Shatroff wrote: > >>> (see [2]) will print the status of the Apache web server, and also the >>> last lines from the logs. You can control how many lines. You can >>> check also with the journal, as I showed up. >> >> I believe it would be a 5-minutes job to add the capability of printing >> last N log entries for a service to `rc-service status`. Using cat, grep > > If I understand you correctly, what you're proposing is an analyzing > tool which works after-the-facts. I wasn't proposing anything. I was just supposing. > I mean extracting the per-daemon logs > from a global log archive whereas systemd works the opposite way, AFAIU. What is a 'global log archive'? Do you mean a single file where all logs go? AFAIK you can set up syslog to log all messages into one file as well as per-service files. So the deal is just to extract configuration from syslog. Of course, if the services are using it, not keeping their own logs as is usually the case of apache. As a multiuser (multi-vhost) webserver admin I have to set up apache to log into users' home directories, so I even don't know how many user logs there really are. And I don't need to, because I've got my own global log. But a user is definitely more familiar with a text file he/she can download via FTP, than with a journalctl wrapper which he has to know how to use (and also be granted SSH access to use), at the least which parameters to specify, if at all usable in such setups. > You solution requires per-daemon extraction rules and have to be > maintained over time. So, postponed to errors. I don't need such 'solutions' to non-existent problems. But if there were a *real* necessity to pretty-print a log's tail in service status, I think it would have been a matter of a proper setup (i.e. the service using syslog, hence a defined log format) and not a heck more complicated. > Definetly not a 5-minutes job. 5 minutes is even too much to type sort of tail -${LINES} ${SERVICE}.log if you know where to look up LINES and SERVICE. -- Regards, Yuri K. Shatroff