Rocco Scappatura wrote:
> Hello,
>
> Is there any step to follow to maintain the policyd database? I fear
> that in heavily loaded mail gateway system, its size could grow
> quickly..
>
> I moreover wish to maintain policyd logs. Could I use syslog and
> logrotate?
I do so.
>
> BTW, is there a log facility that let me to log only essential info
> (just like client, server, sender, recipient and policy matched..)?
Did you see:
# Log level:
# 0 - Errors only
# 1 - Warnings and errors
# 2 - Notices, warnings, errors
# 3 - Info, notices, warnings, errors
# 4 - Debugging
log_level=4
# File to log to instead of stdout
log_file=./cluebringer.log
# Log destination for mail logs...
# main - log to policyd's main log mechanism
# maillog - log mail via syslog
log_mail=main
# Things to log in extreme detail
# modules - Log detailed module running information
# tracking - Log detailed tracking information
# policies - Log policy resolution
# protocols - Log general protocol info, but detailed
# bizanga - Log the bizanga protocol
#
# There is no default for this configuration option. Options can be
# separated by commas. ie. protocols,modules
#
log_detail=tracking,modules,policies,protocols
HTH,
Uwe
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
