Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20050520212240.GA1028@openwall.com>
Date: Sat, 21 May 2005 01:22:40 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: popa3d that *doesn't* use syslog for logging?

On Fri, May 20, 2005 at 03:37:06PM -0500, Mr Duck wrote:
> Any plans in the works for adding a non-syslog mechanism for logging?

No.

> I'd really like to have a way to log popa3d's daily use into a specific 
> file, instead of having to change syslog's setup to manage it.
> 
> I can explain my reasons if requested.

Yes, please.

> Anyway, I'm a C coder as well, and would be happy to implement said 
> changes, but I've never done patches or anything for someone else's 
> code..  typically I'm the only one who ever works on my projects.  (=
> 
> So, what say ye?  Would this be useful for others?

This has been asked for a few times (that's _just_ a few times in
several years!) and noone has provided a valid reason for this so far.

Please keep in mind that one of the design goals of popa3d is
simplicity, and that there're plenty of other POP3 servers out there.

While logging directly to a file isn't a complicated feature to add,
the combined complexity of all imaginable simple features like that is
substantial.

-- 
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.