Hi Jürgen,
thanks for your bug report.
In case of errors greylistd either uses stderr or syslog to inform about
the problem.
As greylistd does not know anything about the configuration of syslogd, it
is hard to decide whether data should be written to syslog or not. Just imagine
that the local syslogd is configured for remote logging.
So I am afraid the process that actually writes data into the file should
take care of disk usage.
Do you have any idea how to solve this issue? Otherwise I would like to
close that bug now ...
Best regards
Thorsten
