[p4] Scripting Login
sweeney at ea.com
Thu Jul 6 07:20:26 PDT 2006
the way I deal with this is to create a croup with a long
timeout and add the script user to that group. If you check the
archives for this list, there was some kind of underflow bug if you
tried to set it to the maximum value allowed, so in my case I have it
set to 1000 days:
[perforce at cgcode ~]$ p4 group -o robots
# A Perforce Group Specification.
# Group: The name of the group.
# MaxResults: A limit on the results of operations for users in
# this group, or 'unlimited'. See 'p4 help maxresults'.
# MaxScanRows: A limit on the data scanned during operations for users
# in this group, or 'unlimited'. See 'p4 help
# Timeout: A time (in seconds) which determines how long a 'p4
# session ticket remains valid (default is 12 hours).
# Subgroups: Other groups automatically included in this group.
# Users: The users in the group. One per line.
[perforce at cgcode ~]$
quis custodiet ipsos custodes -- Juvenal VI, 347-8
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Vander Werf, Bruce
> Sent: 06 July 2006 12:54
> To: perforce-user at perforce.com
> Subject: [p4] Scripting Login
> I have several scripts (MSDOS batch files) I use to manage
> tasks on two different Perforce servers. Where I get hung up
> is on the login. If I haven't logged in to a server for 12
> hours, a login is required and my scripts fails. I haven't
> been able to figure out how to automate the login process, at
> least not with batch files. Anyone have any ideas on this?
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user