a question of apache's logs file for svn

jeff.zhu
jeff.zhu
Can anyone do me a favor to steal the question that how to make the setting of apache for loging the access records exclude a special svn user‘s,so that I can make the jenkin‘s access records be not logging to the logs file for extra disk space any more.  ENV:csvn 5.2.4, redhat7

Last updated

DougR
DougR
I know of no way to restrict Apache logging based on an account name short of modifying the Apache source code and compiling up your own version.  Thinking about this differently, you *could* setup Jenkins to use "svn+ssh" instead and avoid the Apache logging altogether. However, SSHD will still log (although it will be far less logging than Apache).  Cheers.
jeff.zhu
jeff.zhu
DougR;n80699I know of no way to restrict Apache logging based on an account name short of modifying the Apache source code and compiling up your own version.  Thinking about this differently, you *could* setup Jenkins to use "svn+ssh" instead and avoid the Apache logging altogether. However, SSHD will still log (although it will be far less logging than Apache).  Cheers.
  Thanks a lot for DougR‘s reply. But, I‘m thinking about another way to deal with the log trouble via delete the jenkin‘s records with sed and crontab tool at the next day.Probably this can be useful. :rolleyes:
DougR
DougR
Once the log has been rotated so that it is no longer getting appended to, then, yes, you could use sed to shrink it before compression. Might not even need crontab if your log files are being compressed by "logrotate".
jeff.zhu
jeff.zhu
DougR;n80702Once the log has been rotated so that it is no longer getting appended to, then, yes, you could use sed to shrink it before compression. Might not even need crontab if your log files are being compressed by "logrotate".
  Okey!logrotate,great!

1-5 of 5

Reply to this discussion

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