Perforce 2006.1 Command Reference
<< Previous Chapter
p4 fstat
Table of Contents
Index
Perforce on the Web
Next Chapter >>
p4 groups

p4 group

Synopsis

Add or delete users from a group, or set the maxresults, maxscanrows, and timeout limits for the members of a group.

Syntax

p4 [g-opts] group groupname
p4 [g-opts] group -d groupname
p4 [g-opts] group -o groupname
p4 [g-opts] group -i

Description

A group is a list of Perforce users. Use groups to set access levels in the p4 protect form, limit the maximum amount of data that can be accessed from the server by particular users within a single command, and to set the timeout period for p4 login tickets.

To delete a group, use p4 group -d groupname, or call p4 group groupname and remove all the users from the resulting form.

Form Fields

Field Name
Type
Description

Group:

Read-only

The name of the group, as entered on the command line.

MaxResults:

Writable

The maximum number of results that members of this group can access from the server from a single command. The default value is unlimited. See the Usage Notes below for more details.

MaxScanRows:

Writable

The maximum number of rows that members of this group can scan from the server from a single command. The default value is unlimited. See the Usage Notes below for more details.

Timeout:

Writable

The duration (in seconds) of the validity of a session ticket created by p4 login. The default value is 43200 seconds (12 hours). To create a ticket that does not expire, set the Timeout: field to 0.

Users:

Writable,
multi-line

The Perforce usernames of the group members. Each user name must be typed on its own line, and should be indented.

Subgroups:

Writable,
multi-line

Names of other Perforce groups.

To add all users in a previously defined group to the group you're presently working with, include the group name in the Subgroups: field of the p4 group form. Note that user and group names occupy separate namespaces, and thus, groups and users can have the same names.

Every member of any previously defined group you list in the Subgroups: field will be a member of the group you're now defining.

Options

-d groupname

Delete group groupname. The members of the group are affected only if their access level or maxresults value changes as a result of the group's deletion.

-i

Read the form from standard input without invoking the user's editor. The new group specification replaces the previous one.

-o

Write the form to standard output without invoking the user's editor.

g-opts

See the Global Options section.

Usage Notes

Can File Arguments Use
Revision Specifier?

Can File Arguments Use
Revision Range?

Minimal Access Level Required

N/A

N/A

super
(list for p4 group -o)

The Perforce superuser can limit the amount of data that the server returns to the client by setting the maxresults value for groups of users. The superuser can also limit the amount of data scanned by the server (whether returned to the client or not) by setting the maxscanrows value for groups of users.

If either of the maxresults or maxscanrows limits are violated, the server request fails and the user is asked to limit his query.

If a user belongs to multiple groups, the server computes her maxresults value to be the maximum of the maxresults for all the groups of which the user is a member (ignoring any settings still at the default value of unlimited). If a particular user is not in any groups, her maxresults value is unlimited. (The user's maxscanrows value is computed in the same way.)

The speed of most server hardware should make it unnecessary to ever set a maxresults value below 10,000, or a maxscanrows value below 50,000.

The commands that are affected by the maxresults and maxscanrows values are:

Command
Counted Entity
How Affected Users Can Reduce Command Output

p4 changes

changes

Using p4 changes -m numchanges.

p4 changes files

file revisions

Use a more restrictive file pattern on the command line.

p4 diff2

files

Use a more restrictive file pattern on the command line.

p4 filelog

file revisions

Use a more restrictive file pattern on the command line.

p4 files

files

Use a more restrictive file pattern on the command line.

p4 fixes

fixes

The -c changenum or -j jobname flags restricts this command appropriately.

p4 fixes files

files

Use a more restrictive file pattern on the command line.

p4 integrate

files

Use a more restrictive file pattern on the command line.

p4 integrated

file revisions

Use a more restrictive file pattern on the command line.

p4 jobs

jobs

The -e jobquery flag restricts the output to those jobs that meet particular criteria.

p4 jobs files

file revisions

Use a more restrictive file pattern on the command line.

p4 labelsync

files

Use a more restrictive file pattern and the -a flag to build the label's file set in pieces.

p4 print

files

Use a more restrictive file pattern on the command line.

p4 sync

files, as mapped through client view

Use a more restrictive file pattern on the command line.

Related Commands

To modify users' access levels

p4 protect

To view a list of existing groups

p4 groups


Perforce 2006.1 Command Reference
<< Previous Chapter
p4 fstat
Table of Contents
Index
Perforce on the Web
Next Chapter >>
p4 groups
Please send comments and questions about this manual to [email protected].
Copyright 1999-2006 Perforce Software. All rights reserved.
Last updated: 06/23/06