Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> > > On Tue, 24 Feb 2004 13:15:11 -0600, "Tyler Theobald" > <tyler.theobald.junk at cox.net> wrote: > > >I'm referring specifically to the CVSNT temp directory. I > see in some > >posts last year that you were talking through this issue > already, but > >can't tell if you found a fix.....? Thanks! > > > Well, > CVSMailer is not using the CVS temp dir at all so it will not > be the cause of the problem. The only other thing I can think > of is that CVS for some reason feels that it has left a > process behind and is not releasing the temp dir for that > reason. CVSMailer (first invocation) launches itself in a > separate process in order to later collect the data that was > combined from several CVS call to loginfo. But this process > is detached from CVS and should not matter. > > Maybe if you scheduled a task in the middle of the night to > clar out the unwanted folders? Just to add my $0.02. I'm not sure if I saw this behavior before using CVS Mailer, but I *think* I did. (OK, don't take this to the bank and look for credit :) Another thought, though, what is CVSMailer's current directory at the time of running? Could this, somehow, be preventing cvs from cleaning the directory I *definitely* have the same behavior here -- lots of CVS temp dirs hanging around. A simple (using 4nt) script cleans it out. For /a:d %f in (cvs*) do rd /s /q %f Jeff