[p4] 2005.2 stability

[Jason Williams]

One outstanding issue I've encountered has to do with triggers (at least 
on a server running RedHat Enterprise Linux 3).

%clienthost% is null if the IP address of the client doesn't resolve to 
a name.  Because it's null, none of the arguments after %clienthost% 
will be passed correctly to the trigger.  The workaround is to put 
%clienthost% as the last argument to the trigger (though it will still 
be null).

I believe the 2005.1 behavior of %clienthost% substituted %clientip% if 
the client's IP couldn't be resolved.

--Jason

Bennett, Patrick wrote:
> Once the integration problem was fixed, there haven't been any problems
> here.
> The speed improvements in some areas were pretty significant, so I
> definitely recommend the upgrade.
> 
> Patrick Bennett
> 
>> -----Original Message-----
>> From: perforce-user-bounces at perforce.com 
>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Leo 
>> Zelevinsky
>> Sent: Tuesday, May 16, 2006 4:46 PM
>> To: Perforce Users
>> Subject: [p4] 2005.2 stability
>>
>> Hi, everyone!
>>
>> It's been a few months since Perforce released a patched 
>> 2005.2 version that claimed to fix a nasty integration problem.
>>
>> I'd like to push our IT to upgrade our 2004.2 installation, 
>> but am wondering what others' experiences with the new 2005.2 
>> have been. Is it pretty solid? What kind of problems have you 
>> run into?
>>
>> Thanks a lot!
>>
> 
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user



This email and attachments may contain Narus, Inc. confidential material. If you are not the intended recipient, contact the sender immediately and delete all instances of this email and attachments.