-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Beishuizen wrote:
On Fri, 12 Sep 2008 18:02:37 -0400
Greg Larkin [EMAIL PROTECTED] wrote:
Hi Marco,
Right you are! In fact, after my initial logcheck commit, someone
opened a PR stating something very similar to what you noted:
On Sun, 14 Sep 2008 13:00:47 -0400
Greg Larkin [EMAIL PROTECTED] wrote:
Finally, I'll add the members of the wheel group to the logcheck group
so anyone in that group can still read the file as they could before:
On Sun, 14 Sep 2008 21:34:48 +0200
Marco Beishuizen [EMAIL PROTECTED] wrote:
When trying to add root and marco to the logcheck group I get:
...
#grep ^wheel: /etc/group | awk -F : '{ print $4 }' | xargs \ -n1 pw
groupmod logcheck -m
#xargs: -n1: No such file or directory
...
Should I
On Sun, 14 Sep 2008 13:00:47 -0400
Greg Larkin [EMAIL PROTECTED] wrote:
Now the logcheck, root, and glarkin user can all
read /var/log/auth.log, and the logcheck script should work fine. I
hope that clears everything up. If you have any further questions or
problems, please post back here.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Beishuizen wrote:
On Mon, 08 Sep 2008 17:08:35 -0400
Greg Larkin [EMAIL PROTECTED] wrote:
Hi Marco,
I recently committed the upgrade to logcheck, and I am looking into
your problem now. I'll post back here with details once I've figured
On Fri, 12 Sep 2008 18:02:37 -0400
Greg Larkin [EMAIL PROTECTED] wrote:
Hi Marco,
Right you are! In fact, after my initial logcheck commit, someone
opened a PR stating something very similar to what you noted:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127255
The submitter's point
Hi,
After upgrading logcheck from 1.1.1 to 1.2.54 I suddenly get errors of
logcheck not working correctly:
...
Warning: If you are seeing this message, your log files may not have
been checked!
Details:
Could not run logtail or save output
Check temporary directory: /tmp/logcheck.6IZZmq
Also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Beishuizen wrote:
Hi,
After upgrading logcheck from 1.1.1 to 1.2.54 I suddenly get errors of
logcheck not working correctly:
...
Warning: If you are seeing this message, your log files may not have
been checked!
Details:
Could not