Thanks for all your help Doug. On Fri, 2008-02-08 at 10:29 -0500, Doug McNeil wrote: > Your are right about (2). There should be a guard around the "if" > block at line 221 in CVS.pm to only allow execution of the block when > "$self->consolidate_cvs_messages() == 1". (I guess no "consolidation" > actions should apply anywhere if this flag is not set :-)
I guess this was the problem. Apparently when I attempted to conditionally enable this feature I broke your well-tested, working solution. After I corrected this I no longer see .scmbug_consolidated_* files, and the log comments are actually consolidated. > with an activity it calls its ''close'' function. I might be able to > look at this over the next week or so... If you manage to do that, it'd be great. I am confused with the current implementation. > But is this more related to a generic "session" handling issue? For No, in this instance I actually broke everything myself :} > the couple of months I used SCMBUG with this feature it worked well > in my Linux environment. But session handling has enough holes in it > to drive a truck through! In principle it depends on every concurrent > session having a unique user name (I do not think that using the > parent pid has any mitigating effect on session). So any use case It seems that different parent pids are created at least in Linux. Don't know how CVSNT reacts to this. > where this is not the case will suffer concurrency issues. For > example an environment where people "share" a CVS user (a daemon user > for instance) could have concurrency issues. Although I do not know > enough I understand your suspicions. Hmmm....
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
