On Mon Oct 14 13:41:40 2013, Andreas Schulze wrote:
> I plan a migration to dovecot and have concerns about the amount of logged
> data.
> On a testsystem dovecot produced 1TB syslog per day with a comparable amount
> of pop3 sessions.
>
> The current server log to STDOUT which is connected to
Hi,
writing >1 TB per day sounds not wise.
Use syslog-ng or similar to define log destinations to STDOUT / STDIN
like multilog and omitting the "write to disk" part.
E.g., using syslog-ng with the MongoDB target and a capped collection
enables a similar circular buffer with the search t
Am 14.10.2013 12:45 schrieb Ben:
> >The current server log to STDOUT which is connected to multilog
> >(circular buffer, http://cr.yp.to/daemontools/multilog.html)
> >That way I can have a look at the last activities to any time.
> What's wrong with good old sysslog, or why don't you use Splunk or
On 14/10/2013 12:41, Andreas Schulze wrote:
Hello,
I plan a migration to dovecot and have concerns about the amount of logged data.
On a testsystem dovecot produced 1TB syslog per day with a comparable amount of
pop3 sessions.
The current server log to STDOUT which is connected to multilog
(ci
Hello,
I plan a migration to dovecot and have concerns about the amount of logged data.
On a testsystem dovecot produced 1TB syslog per day with a comparable amount of
pop3 sessions.
The current server log to STDOUT which is connected to multilog
(circular buffer, http://cr.yp.to/daemontools/mul
