[mythtv-users] Notification of conflicts

[f-myth-users at media.mit.edu]

    > Date: Sat, 19 Sep 2009 11:12:12 -0400
    > From: "Michael T. Dean" <mtdean at thirdcontact.com>

    > I even gave links to "real" programs that monitor logs--allowing you to 

...which I'm sure will be useful to some people, but are entirely too
heavyweight for what I'm doing, which is why I spent less time rolling
my own than it would have taken to configure any one of those to do
what I wanted.

I'll assume you were trying to be helpful, though, so I'll thank you
anyway, and hopefully some other user will find those links useful.

    > get notifications real time--so he wouldn't have to use hacked-together 
    > bash scripts with 10's of instances of tee and grep and ...

I know you get a lot of joy from bashing everything I say, but you
don't have to resort to stuffing words in my mouth to do it.

Did I say "10's"?  No, I did not.

In fact, I have precisely -one- filter script that one of those
logging programs might help with, and that's assuming that it also did
the sort of notification I wanted.  I've got another couple of tees in
there that set flags so I can know, absolutely, when the scheduler is
and isn't running.  And that's it; the filterN stuff was a pedagogical
example that I thought might help others who wanted to extract
different log outputs to different places.

So as much as it offends you that I've actually written my own code
to solve my own problems, that's what I've done.  I've typically not
bothered offering most of the code I've written to the community,
because I'm tired of spending my time defending myself while trying
to give away solutions.  This is a fine example.