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

svnversion & svn st

From: Bill Comisky <bcomisky_at_pobox.com>
Date: 2003-08-22 05:51:47 CEST

I noticed that when I run 'svnversion' and 'svn st' it will take a "long"
time (~12s on /svn source tree) to execute, and then after the first
execution it will run quickly (< 1s). Then I noticed this behaviour every
day, even though I hadn't accessed the directory tree in question. Or
hadn't accessed it directly anyway... My best guess is a backup script or
updatedb cron job is accessing the directories.

I just did a 'find . -ctime -2', 'find . -mtime -2', and 'find -atime -2'
at the root of the tree. ctime (status last changed) and mtime (last
modified) showed nothing for the last 2 days. atime (last accessed)
showed all of the contents of the .svn subdirectories and all of the
directories. I did just run 'svn st', so that makes sense. So what do
'svnversion' and 'svn st' use as an indicator to recheck the directory
contents?

This is probably a non-issue for most, but I call svnversion from my
(non-compiled) code to get the revision # for my single-revision working
copy. So the first time I do that every day I have to wait an agonizing
>10s (which is an hour a year I'd rather do something else with ;)

bill

--
Bill Comisky
bcomisky@pobox.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 05:52:38 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.