[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Logfile growth

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-07-30 17:22:29 CEST

From: "C. Michael Pilato" <cmpilato@collab.net>
> "Simon Large" <slarge@blazepoint.co.uk> writes:
>
> > I cannot find anything about this in the FAQ, either for SVN or
Tortoise.
> > Should I expect the logfile to grow without bounds or have I missed a
vital
> > admin process somewhere? Once the actions have been carried out on the
> > database, why is the logfile still needed?
>
> The logfile *set* (more than one logfile) will grow without bounds,
> but a particular logfile should only grow to about 1 Mb (as the result
> of Subversion's custom configuration of Berkeley DB). Generally, once
> a logfile reaches the 1Mb point, Berkeley will start a new logfile.
> It is only when Berkeley has finished using a logfile (meaning it has
> begun a new one) that list-unused-logfiles will display it. You will
> always have at least one logfile in use at any given time.
>

Thanks guys,
By some quirk the log file had reached 1023K when I stopped testing. Had I
done one more update, I would have seen the new logfile appear. The
information you have given would be worth including in the manual and/or
FAQ.

Also, it looks like SubVersion is set up to delete the redundant logfiles.
The DB_CONFIG file has 'set_flags DB_LOG_AUTOREMOVE',
but the logfiles do not appear to get deleted immediately they become
redundant, although they do disappear later on, which was a little confusing
to start out.

Simon.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 30 18:32:20 2004

This is an archived mail posted to the Subversion Users mailing list.