Groups > linux.debian.user > #198682

Re: non-blocking stdin from bash

From	Jim Popovitch <jim@k4vqc.com>
Newsgroups	linux.debian.user
Subject	Re: non-blocking stdin from bash
Date	2018-08-13 00:50 +0200
Message-ID	<wm7ln-6YG-1@gated-at.bofh.it> (permalink)
References	(3 earlier) <wlU4N-7FM-1@gated-at.bofh.it> <wm1zj-3BT-7@gated-at.bofh.it> <wm2F3-4cb-3@gated-at.bofh.it> <wm2OJ-4fi-7@gated-at.bofh.it> <wm6Sm-6ML-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Mon, 2018-08-13 at 10:13 +1200, Richard Hector wrote:
> On 13/08/18 05:57, Jim Popovitch wrote:
> > Interesting.  I'm using it via a cron script like so:
> > 
> > * * * * *  grep "unusual" /opt/logs/* | /opt/notify.sh `hostname`;
> 
> I don't know what's in notify.sh, but it looks to me like you're
> going to get notified every minute for all the unusual log entries,
> whether you've already seen them or not?

That was just an example of what I'm doing.  In reality logtail's in
there, but it made the example line too long.

> Have you looked at logcheck or other similar existing solutions?

Yes, i use logcheck religiously, despite the absolute lack of logcheck
rules maintenance that exists in most packages not installed on a
default system (looking at you nginx, postfix, bind9, cron, clamav*,
openvpn, dovecot, opendmarc, monit, and openntpd).   I'd submit the
improvements to the appropriate maintainers, but I dislike rejection. 
;-)

-Jim P.

Thread

non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-12 00:10 +0200
  Re: non-blocking stdin from bash <tomas@tuxteam.de> - 2018-08-12 00:50 +0200
    Re: non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-12 07:30 +0200
      Re: non-blocking stdin from bash <tomas@tuxteam.de> - 2018-08-12 10:40 +0200
        Re: non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-12 18:40 +0200
          Re: non-blocking stdin from bash <tomas@tuxteam.de> - 2018-08-12 19:50 +0200
            Re: non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-12 20:00 +0200
              Re: non-blocking stdin from bash <tomas@tuxteam.de> - 2018-08-12 22:00 +0200
              Re: non-blocking stdin from bash Richard Hector <richard@walnut.gen.nz> - 2018-08-13 00:20 +0200
                Re: non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-13 00:50 +0200
                Re: non-blocking stdin from bash Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-13 15:00 +0200
                Re: non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-13 16:40 +0200
                Re: non-blocking stdin from bash Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-13 16:50 +0200
                Re: non-blocking stdin from bash Jim Popovitch <jim@k4vqc.com> - 2018-08-13 17:00 +0200
                Re: non-blocking stdin from bash Dan Purgert <dan@djph.net> - 2018-08-13 17:10 +0200
                Re: non-blocking stdin from bash Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-13 17:10 +0200
                Re: non-blocking stdin from bash Dan Purgert <dan@djph.net> - 2018-08-13 17:30 +0200
                Re: non-blocking stdin from bash Richard Hector <richard@walnut.gen.nz> - 2018-08-14 08:10 +0200

csiph-web