Displaying 3 results from an estimated 3 matches for "my_rul".
Did you mean:
my_rule
2005 Nov 08
1
It's not filtering this one specific line...
I keep seeing...
"Nov 7 23:08:09 ns1 amavis[24086]: (24086-06) WARN: all primary
virus scanners failed, considering backups"
And no matter what I try to make a rule filter for it, it won't go
away! I've tested my rules by doing `cat /var/log/mail.log | egrep
"$my_rule"` and it would work and scroll out all the matched output.
Here is one of the rules I tried...
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ amavis\[[0-9]+\]: +(\([-0-9]+\) +)?
WARN: all primary virus scanners failed, considering backups
I tried shortened versions, and guaranteed versions like just &...
2008 Mar 16
1
Problem with rules being 'ignored'
Hey there, sorry to bug you,
I've ran into a little problem conscerning a logcheck-rule I just wrote.
I use logcheck and logcheck-database on Debian Etch. When logcheck
reports me something I don't want it to, I normally write a rule to
match that logentry and put it in a file called my_rules in
/etc/logcheck/ignore.d.server/ ... that worked perfectly fine. Until
that rule:
Logcheck keeps reporting me that:
Security Events
=-=-=-=-=-=-=-=
Mar 16 15:45:48 uhweb64206 postfix/smtpd[21799]: NOQUEUE:
reject_warning: RCPT from unknown[220.231.197.4]: 504 5.5.2
<220.231.197.4>: Helo...
2003 Jun 13
8
Oracle SQL*Net through Shorewall
Hello all,
I am a newbie to Linux firewalls, and am trying to setup shorewall to allow connections from an Oracle client to an Oracle Server. The client tries to connect to the server via port 1521 (it works fine) and once the first connection has been successful, the server sends a redirect to the client to a random high port. So, when the client tries to connect again to the sevrer on that port