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.
Bo Berglund wrote: > 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... That's how it's supposed to work - when the loginfo script is called its current directory is a working sandbox... in the case of client/server this is the server temp directory. From this you can get extra information about the commit. > Would be good to know what the conditions are on the cvsnt side for removing or > not removing the temp folder... It always tries, but failure isn't fatal - partly because it happens after the client has disconnected and partly because on Unix the /tmp is usually cleared on each boot anyway. Tony