Displaying 3 results from an estimated 3 matches for "maswan".
Did you mean:
marwan
2008 Mar 19
1
End of search string question
How do I tell LogCheck that I don't care what's in the rest of the search
string?
^\w{3} [ :0-9]{11} m0n0wall ipmon\[[0-9]+\]: [0-9:]{8}\.[0-9]{6} xl0 (@
0:3|@100:3) (b|p) 192\.168\.2\.[0-9]{1,3} -> [0-9.]{7,15} PR igmp len
[0-9]{2} \([0-9]{2}+\) IN$
^\w{3} [ :0-9]{11} m0n0wall ipmon\[[0-9]+\]: [0-9:]{8}\.[0-9]{6} xl0 (@
0:3|@100:3) (b|p) 192\.168\.2\.[0-9]{1,3} -> [0-9.]{7,15} PR
2009 Apr 07
1
Bug#515156: Same bug after removal + reinstall
I ran into the same problem after somebody uninstalled logcheck and I
re-installed it.
It turned out that the ownership of /var/lock/logcheck where root:root -
sudo chown logcheck:logcheck /var/lock/logcheck solved it.
I see that there already is a check for the permissions in the postinst
which (as far as I can see) *should* have fixed the permissions and
ownership there.
When re-installing
2007 Sep 24
1
Bug#443908: /etc/logcheck/ignore.d.server/bind: [bind] unexpected RCODE (NOTIMP)
Package: logcheck-database
Version: 1.2.61
Severity: wishlist
File: /etc/logcheck/ignore.d.server/bind
After #437891, I got yet another new "unexpected RCODE", this time
"NOTIMP". As I was starting to get pissed off, I copied the whole list
out of lib/dns/result.c, in an attempt to put an end to my headache.
If you insist on using an enumeration instead of ".*",