svnserve Log file configuration

satheesh
satheesh
Am using svn 1.7.4 on windows 7    How can i configure log file    For a single client log in(open repository using Tortoisesvn) process it generate lot of logs which is not understandable.      7668 2012-08-13T09:21:53.673494Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.677495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.679495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 -  7668 2012-08-13T09:21:53.679495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-latest-rev  7668 2012-08-13T09:21:53.679495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos reparent /  7668 2012-08-13T09:21:53.680495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos check-path /@13  7668 2012-08-13T09:21:53.680495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-dir / r13 props  7668 2012-08-13T09:21:53.680495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.682495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.682495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-latest-rev  7668 2012-08-13T09:21:53.682495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos reparent /  7668 2012-08-13T09:21:53.682495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos stat /@13  7668 2012-08-13T09:21:53.682495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-locks /  7668 2012-08-13T09:21:53.683495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.683495Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-latest-rev  7668 2012-08-13T09:21:53.683495Z 127.0.0.1 harry Users/venkateshkumarg/Desktop/SVN/svn1.7/Repos get-dir / r13 text  7668 2012-08-13T09:21:53.712498Z 127.0.0.1 harry Users/venkateshkumarg/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.714498Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.717499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) /tags SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-latest-rev  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos reparent /tags  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos stat /tags@13  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) /Test SVN/1.7.2 TortoiseSVN-1.7.4.22459  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-latest-rev  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos reparent /Test  7668 2012-08-13T09:21:53.723499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos stat /Test@13  7668 2012-08-13T09:21:53.724499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-locks /Test  7668 2012-08-13T09:21:53.724499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-dir /Test r13 text  7668 2012-08-13T09:21:53.724499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-locks /tags  7668 2012-08-13T09:21:53.725499Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos get-dir /tags r13 text         I need to control logs,  That is for certain events such as log in, get i need to log single entry in log file... Like     [Event-name] success [user-name] - time     eg: OpenRepos success harry 2.39-8/13/12   Set label Success harry 2.45-8/13/12    is it possible in svnserve ??? if it is pls help me....    thanks in advance

Last updated

andyl
andyl
As has been explained to you at least twice before, you are doing this wrong. You cannot use the logfile to control access to your repository because the log file records what has happened after the fact. If you're trying to perform logfile analysis after the fact as a method of controlling/monitoring people, you are still approaching it wrong - there are lots of things that can be done which will bypass the server and any logging, entirely. Explain why you think you need to do this and people can help you better.    Subversion has path-based authorization built in and that is what you must use to control access to the repository.
satheesh
satheesh
Hi andyl,   am not trying to use log file to control the repository access. I am trying to reduce complexity of log file. For a single Event(opening a Repository or Commit) it generates more logs like above i have mentioned... thats why i need to reduce log entries for single event...
satheesh
satheesh
Pls can anyone help me to do this ....
vinnyjames
vinnyjames
What appears in the logs for failed authentication? I know apache has better logging. It may be the case that the first log which includes the username only appears if the authentication is successful:  7668 2012-08-13T09:21:53.673494Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  
andyl
andyl
satheesh;120664Hi andyl,     am not trying to use log file to control the repository access. I am trying to reduce complexity of log file. For a single Event(opening a Repository or Commit) it generates more logs like above i have mentioned... thats why i need to reduce log entries for single event...
   Why do you think you need to do this in the first place? The log data is there to trace what has happened with access to the repository. If you want to change what's logged, you have to change the code itself - IOW, create a custom build of Subversion for yourself.
satheesh
satheesh
vinnyjames;120668What appears in the logs for failed authentication? I know apache has better logging. It may be the case that the first log which includes the username only appears if the authentication is successful:  7668 2012-08-13T09:21:53.673494Z 127.0.0.1 harry Users/satheesh/Desktop/SVN/svn1.7/Repos open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.7.2 TortoiseSVN-1.7.4.22459  
  Can i format the log file like " IP User Request Repository " for easy understanding ???
andyl
andyl
satheesh;120673Can i format the log file like " IP User Request Repository " for easy understanding ???
   What stops you from writing a script to perform that parsing? Compared to a lot of other logs I've had to deal with, that's very parseable.    Apache's built-in logging lets you change the log format. svnserve's is not as sophisticated.
satheesh
satheesh
ok then where & how can i redirect the logs to my script to parsing & formating ???
andyl
andyl
You don't redirect the logs (well technically you could, but then you'd also be throwing away log data which may become beneficial later), you write a script to read the logs that exist and point it at them to produce the output you desire when you need to perform your log analysis.    But you still haven't made clear what you want to achieve. As I've pointed out several times now, there are ways of getting things from the repository which aren't necessarily going to show up the way you'd expect in the logs (or at all). If you intend to use this as a way to monitor employee usage, it will fail.
satheesh
satheesh
andyl;120678 If you intend to use this as a way to monitor employee usage, it will fail.
  No am not trying to use this logs to restrict or monitor the employee usage. am trying to keep the logs in understandable format & reduce log entries.  It is possible right ???
andyl
andyl
satheesh;120692No am not trying to use this logs to restrict or monitor the employee usage. am trying to keep the logs in understandable format & reduce log entries.    It is possible right ???
 Once again, you cannot change how svnserve writes its logs, without compiling a custom version or doing some other system-level trickery which will have the side-effect of dropping logged data that may become important later. What you can do is write your own script to parse the logs when you need to perform analysis.    How often are you looking at the logs such that it's a major burden to read them & sift through the amount of data that's in them? The logs seem verbose because that verbosity is needed to capture meaningful data about what's happening with your repository, so cutting them down as you describe will make them less useful.
satheesh
satheesh
Thanks,  am running svnserve in cmd prompt   C:\SVN\bin>svnserve.exe -d --listen-port 3399 --log-file log.txt  here make use of log.txt and parse this log file using own script to generate the separate log file. This is a soln which u have told right?
andyl
andyl
satheesh;120696Thanks,    am running svnserve in cmd prompt    C:\SVN\bin>svnserve.exe -d --listen-port 3399 --log-file log.txt    here make use of log.txt and parse this log file using own script to generate the separate log file. This is a soln which u have told right?
   You should be running it as a service, not manually from the command prompt.    I haven't given you any "solution" here. You've been asking about how to destroy the long-term usefulness of your logfiles, and I've been telling you not to do it & what to do instead.

1-14 of 14

Reply to this discussion

You cannot edit posts or make replies: You should be logged in before you can post.