From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/966 Path: news.gmane.org!not-for-mail From: "George Georgalis" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: clear proc log Date: Fri, 30 Dec 2005 17:00:09 -0500 Message-ID: <20051230220009.GO28661@sta.duo> References: <20051123132508.GA25346@sta.duo> <20051129124728.7641.qmail@d5b81a4de6596e.315fe32.mid.smarden.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1135980024 26280 80.91.229.2 (30 Dec 2005 22:00:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 30 Dec 2005 22:00:24 +0000 (UTC) Original-X-From: supervision-return-1202-gcsg-supervision=m.gmane.org@list.skarnet.org Fri Dec 30 23:00:21 2005 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1EsSIJ-0004Pq-7o for gcsg-supervision@gmane.org; Fri, 30 Dec 2005 23:00:15 +0100 Original-Received: (qmail 6147 invoked by uid 76); 30 Dec 2005 22:00:35 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 6142 invoked from network); 30 Dec 2005 22:00:35 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20051129124728.7641.qmail@d5b81a4de6596e.315fe32.mid.smarden.org> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:966 Archived-At: guess I've been busy... haven't checked this list in a while... On Tue, Nov 29, 2005 at 01:47:28PM +0100, Gerrit Pape wrote: >On Wed, Nov 23, 2005 at 08:25:09AM -0500, George Georgalis wrote: >> I've got some proc log I'd like to clear from the runsvdir entry in ps. >> With readproctitle, I'd make a service and run "once" >> >> #!/bin/sh >> yes '' | head -4000 | tr '\n' . >> >> But that is not working under runsvdir. How should I go about >> clearing the dots? Also, any suggestions on adding the service > >runsvdir only writes stderr to the readproctitle log, not stdout. >Adding `exec 1>&2` to the run script should help. Thanks. I discovered adding >&2 to the pipeline worked, but exec seems cleaner. >> which is barfing to the log, and making each entry longer? > >I'm not sure I completely understand what you mean, any examples? When I've got a bunch of services and errors rolling through readproctitle, it's not always apparent which one is sick, pretty much got to test each service and it's log to see which one is broke -- actually watching the PIDs change in ps seems the easiest way to identify. I don't really know what I meant by "making each entry longer"; however, when a service, run script or its log/run is broken, the path to ./run or ./log/run is not always apparent. If runsv (or possibly runsvdir) (optionally) provided the path (maybe just additionally the dir the script runs from, the link in service/), tracking down errors would be easier. <-- feature request Maybe this requires a "cd ../" before executing the path to the given run script -- which sounds awkward, I'm not sure how to implement this. Lately, I've been porting my daemontools supervise installations to runsv and I'm really pleased with the improvements. The procedure to remove a service, for example, is greatly improved. Thanks! // George -- George Georgalis, systems architect, administrator < http://galis.org/ cell:646-331-2027 mailto:george@galis.org