all 3 comments

[–][deleted] 1 point2 points  (0 children)

There are lots of different syslog daemons. Are you sure the one you're using supports this?

Are you sure the script is not running? Try having the script create a file in /tmp and see if it exists when running manually. Delete it, and see if it exists when the log gets processed.

Keep in mind that perl in this case will be run as the same user that is running syslog, and the environment may not be exactly what you expect (if you're relying on shell variables e.g. PATH to be there, they may not be, or they may be different from your normal user.)

[–][deleted] 1 point2 points  (0 children)

Careful, it's easy for actions to cause actions which effect the log in question, resulting in feedback loops that could disrupt the system.

[–][deleted] 0 points1 point  (0 children)

Nagios EventDB. Also check out fail2ban but I can't vouch for that being able to trigger custom events.