An example of all i've been talking, is ProFTPD, of logging goes to syslog, or you can make your own custom log to *SQL. All this talk about logging, is for the login/logout values, and for the received messages log? What's your sentence Paul/Aaron?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Stone Sent: quarta-feira, 12 de Setembro de 2007 20:08 To: DBMail mailinglist Subject: Re: [Dbmail] Log table On Wed, Sep 12, 2007, Marc Dirix <[EMAIL PROTECTED]> said: >> Putting the log_level to 3 , that yes is going to kill the server. >> > > This is so not true! > Our logs are also a lott bigger than 80MB a day. > > I must say, dbmail logging (@level 3) is still lacking (as stated > before), however since I didn't > patch it myself I should really not keep going on it. However it > should *not* be replaced by database > logging just because the current syslog is lacking. It actually just dawned on me that calling it a 'logging table' is making us think along the lines of free-form syslog entries. How about 'audit table' with structured records of major events and which account made them? Aaron _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
