clear proc log

clear proc log

[George Georgalis]

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
which is barfing to the log, and making each entry longer?

// George


-- 
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org

Re: clear proc log

[Gerrit Pape]

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.

> which is barfing to the log, and making each entry longer?

I'm not sure I completely understand what you mean, any examples?

Regards, Gerrit.

Re: clear proc log

[George Georgalis]

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 <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org