[cvsnt] Re: cvstemp dir not clearing itself due to CVSMailer
Bo.Berglund at system3r.se
Thu Feb 26 11:56:01 GMT 2004
I did not know that the current temp dir contains the involved files...
Additional questions then:
What is the file structure of the temp "sandbox" at the time loginfo is called?
Are all module files there or only the ones affected by the command?
Are we talking about "normal" files as opposed to RCS files?
Could the file list actually be compiled by listing the files in te current dir?
And are there CVS metadata dirs also?
I know that for multi-folder commits the loginfo script gets called several times,
once per subdirectory.
So will the same directory structure be created in the tempdir as well?
And will the current dir change for each invocation of the loginfo script?
Or will the full structure be there when the first call is made?
Or maybe there will be e different temp dir for each call to the loginfo script?
BTW, this morning I installed my modified CVSMailer (which changes the current
dir on start ) in the work server and so far there are no temp dirs remaining.
And I know there has been at least 10 or so commits since. Seems to work.
I will update the installer ASAP, but I will go away on vacation for a week
so it might not happen until I am back. Meanwhile the new exe file is separately
available as a link on my page.
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Tony Hoyle
Sent: den 26 februari 2004 11:38
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Re: cvstemp dir not clearing itself due to
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.
cvsnt mailing list
cvsnt at cvsnt.org
More information about the cvsnt