Subject: Re: newsyslog and script execution instead of sending signal to process
To: NetBSD-current Users's Discussion List <firstname.lastname@example.org>
From: Brett Lymn <email@example.com>
Date: 07/18/2007 11:02:19
On Tue, Jul 17, 2007 at 02:26:32PM -0400, Greg A. Woods wrote:
> Note too that it's poor design and total lack of integration into the
> overal system pretty much mandates that it have bot the pre and post
> command hooks that it has.
I'm sorry - I don't believe that you are competent to comment on the
implementation of logadm at all. You have just looked at the man
pages, you have no experience with running it. There is a lot of
subtlety in the tool that you have missed. I don't care to try and
teach you about it. Go try and _really_ use the tool and then come
back - prior to that you are just pontificating.
> No, it's not inelegant at all -- that's cron's ideal kind of job, that's
> what it does best, that's what it was designed to do.
> Neither of these things are newsylog's job.
Rubbish. newsyslog is meant to manage logs, part of managing those
logs is ensuring that the logs are moved in a manner that ensures
those logs are consistent and correct - this means interacting with
the applications performing the logging.
What you are suggesting is filling up the crontab with bunches of
little scripts all watching directories waiting for Stuff To Turn Up.
Or are you suggesting you roll all that up into one script? and have
a config file?