> > I suspect it's because you're using a relative path (./gigaspaces). You'll > need the full path to it from cron which may not be in the same directory > you were in.
Thanks for your reply. I am using an identical copy of the file on my workstation and some excerpts from the logs. But I ran the egrep check on the server itself using the actual logcheck configuration and log file (fed it to "egrep -f") and it works as expected - stack traces are filtered out. But when logcheck runs from cron then the stack traces are not filtered out (using the same config file). Its bizarre - I'll see what else I can find out. Cheers, Fred. > > > -- > Chris Jackson > Shadowcat Systems Ltd. > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/y2sff5ddf021004290429ta9da82dcje39f9482556a3...@mail.gmail.com
