Hi Paolo
On 27/Apr/2012 13:19, Paolo Lucente wrote:
Slightly late but, for what is worth, to agree with your latter ideas.
One thing i wanted to specify is the following:
* You can't specify arguments to the script, so you'd need uniquely
named scripts for each plugin. Even though the only difference would be
in which directory it should look for files.
True, no arguments but environment variables are set for you. For example
database name, table name, etc. are all available. This is documented in:
docs/TRIGGER_VARS in the standard pmacct distribution tarball (the doc is
in turn referenced by the sql_trigger_exec entry in CONFIG-KEYS).
That would help me if I were to be using the SQL plugin, and not the
print plugin. As stated at http://www.pmacct.net/CONFIG-KEYS-0.14.0:
"In the print plugin a simpler implementation is made: triggers can be
fired at each 'print_refresh_time' only and no environment variables are
passed over to the executable."
I guess there is some room for improvement here ;-) (no offense meant,
pmacct is a great piece of software as it is)
Regards,
Ruben Laban
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
