You can read /var/log/xxxxx (where xxxx is the syslog category you chose to log the message) and do anything you like with it. Example:
tail -f /var/log/messages | grep "CLOSE" | 'script to do something with the message' I don't recommend the above for large numbers of filters (the tail command is expensive for busy hosts -- you'd probably want to configure syslog to write the messages directly to a pipe for busy systems; see 'man syslogd.conf'), but you can experiment trivially with the above. This is what I suggested earlier when you were asking about VSFTP exits. David Boyes Sine Nomine Associates > Currently, on the z/OS the NDM and FTP has an userexit after the file > is created. I have two problems on the LINUX, the VSFTPD and NDM > does not have an userexit... and the file is create at the OPEN - is > still being write to. The solution for the VSFTPD was filter the > "UPLOAD" > and the destination to a program . . The "UPLOAD" is like Closing a > file. I like to know how does NDM:CONNECT creates the log... > Can I use syslog-ng to filter a CLOSE/COMPLETION of a file and > execute a command in the destination statement??? > The product has not been installed and I am not the person > installing. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
