Re: COMMON LOGGING FORMAT

[Alexey M. <al...@hs...>]

>>>>> "AM" == Alexey Morozov <mo...@no...> writes:

 >> - are there any more logging objects?
 AM> Probably we should add not objects, but some kind of
 AM> "state"/"stage" to loggin', i.e. when a user logs in (just logs
 AM> in, right in checkpassword, an appropriate line goes to log, smth
 AM> like this: %U (%I) logs in (status: [success/failure]

This particular case is going to be handled from the 'cvs-pserver', I
believe.

(I have to note that there is a strong trend towards making :pserver:
in all of its varieties the de-facto only access method.)  Local
repositories are out of scope for cvs-nserver project, and the :ext:
method is not that different from the local repository.



The more I think about it, the more I like the idea to use syslog()
everywhere, and not bother about log file synchronizations, etc.  I
believe that syslog-ng could provide more than adequate filtering for
the cvs server messages.  What do you think?  I really don't want to
bother with my own logging, because I don't see any rationale for
that.


As for logins: I proposed separate format of authentication log
entries:

	login vasya from 123.45.67.89 in /repos

or
	LOGIN-FAILURE bad-guy from 10.9.8.7 in /top-secret-repos



ACL violations are logged like that:

        access-denied vasya from 1.2.3.4 in /top-secret-repos to module/sdir/foo.c for access


All the operations are logged "as always":

	checkout module/sdir/bar.c (rev 1.14) in /repos, etc, etc.

--alexm