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 Wed, 26 Jan 2005 22:05:11 +0100, Bo Berglund <bo.berglund at telia.com> wrote: >I have seen that the parsing of the users and/or loginfousers file is >incorrect when there are \ in the username or so it seems from the >logs. In my case it found user DOMINO in both the -r argument and in >the loginfousers or users file... >I have to dig into that some more, that is definitely not correct >behaviour. So this is now corrected, turns out that I did a compare on the command line username on the users file entries and registered a hit if the username on command line matched the start of a users file line. So DOMINO matched DOMINO\bob there... And if you would have several domain users with the same starting characters as one user then it would hit falsely: With this in the users file: DOMINO\bobby DOMINO\bob user bob would never get an email because bobby would compare first. This is fixed now, but I don't have a solution for the backslash gobbling short of changing the syntax in the command line and the users file to be using forward slashes. But then I wonder what will happen when notify triggers? In that case CVS is supposed to go to the users file all by itself and parse out data. CVS has a built in block of triggering notify to the user who triggered the action, how will that work here??? If CVSNT then uses usernames with backslashes it won't find anything in the users file.... BTW, come to think of it, how does CVSNT store the watchers in this case? If the user is a domain user he surely will carry his domain prefix in his login, right? So what is CVSNT doing with that in a watch and on a notification trigger? Final note: the parsing done on the users and loginfousers files are case sensitive! /Bo (Bo Berglund, developer in Sweden)