[p4perl] Problem Running P4Perl Based Triggers After Linux SystemUpdate

Tony Smith tony at smee.org
Wed May 7 13:28:18 PDT 2008


Hi Scott,

Scott Lavender wrote:
> Also, in reference to the P4PASSWD error, here is the output showing my
> long term(permanent) ticket:
>
> [root at perforce test]# p4 tickets
> 192.168.1.61:1666 (build) B740A553FDFAAE9A3C85DFD19485DE5F
> [root at perforce test]# p4 login -s
> User build ticket expires in 27727 hours 42 minutes. 
>
>   
This is definitely an authentication problem. I think it might be that 
(2007.3?) 'p4' is storing the ticket under a different 'key' in the 
tickets file from the one that (2005.2 API) P4Perl is looking for. There 
have been some changes in this area, for example to support central 
authentication servers properly.

Can you download a 2005.2 'p4' for your platform, use that to run a 'p4 
login', and see if that adds another ticket to your list (and resolves 
the problem)?

Thanks,

Tony



More information about the p4perl mailing list