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.
Involved, yes - but how? It may well be that somehow CVS senses that a process has been spawned off and therefor does not clear out the folder. One possibility might be that CVS when launching the loginfo script command sets the current dir to this temp dir. THis might cause the deletion of the folder to fail because "someone" is there... I will have a look at the CVSMailer code and see if I can CD to the application dir or similar to solve the problem. Would be good to know what the conditions are on the cvsnt side for removing or not removing the temp folder... Also it wold be good to know if cvsnt actually sets the current dir for the loginfo process as the temp dir. BTW, I just checked our production server and I also found tons of folders in the temp dir, all named cvs-srvxxxx where xxxx is a number. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Tyler Theobald Sent: den 25 februari 2004 16:18 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: cvstemp dir not clearing itself due to CVSMailer > 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. Well, if I set the CVSMailer delay to 0, the problem goes away. Put it back to 10000 and the problem comes back, so CVSMailer is obviously involved.