-
I'm not sure what calls are being made to call this,
but KDiff3 takes around 30-40 seconds to start on my
machine. Some quickie monitoring shows that it's
doing a lot of active directory calls. Is there any
chance the KDiff3 code is doing some queries for user
information on startup?
It's worth noting that I'm in a remote office - the
active directory is a few thousand miles...
2006-10-13 17:27:33 UTC in KDiff3
-
jmm committed patchset 42 of module tiobench to the Threaded I/O tester CVS repository, changing 2 files.
2003-12-22 03:44:53 UTC in Threaded I/O tester
-
jmm committed patchset 41 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-12-22 03:06:59 UTC in Threaded I/O tester
-
jmm committed patchset 40 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-12-22 02:53:18 UTC in Threaded I/O tester
-
jmm committed patchset 39 of module tiobench to the Threaded I/O tester CVS repository, changing 5 files.
2003-12-19 05:28:16 UTC in Threaded I/O tester
-
jmm committed patchset 38 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-11-19 06:12:04 UTC in Threaded I/O tester
-
jmm committed patchset 37 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-11-19 06:11:31 UTC in Threaded I/O tester
-
jmm committed patchset 36 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-11-19 04:38:19 UTC in Threaded I/O tester
-
jmm committed patchset 35 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-11-19 04:38:05 UTC in Threaded I/O tester
-
jmm committed patchset 34 of module tiobench to the Threaded I/O tester CVS repository, changing 1 files.
2003-11-18 23:16:30 UTC in Threaded I/O tester
