{"id":1718,"date":"2017-12-06T04:57:12","date_gmt":"2017-12-06T04:57:12","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=1718"},"modified":"2025-02-01T22:39:35","modified_gmt":"2025-02-01T22:39:35","slug":"basic-perforce-administration","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/basic-perforce-administration\/","title":{"rendered":"Basic Perforce Administration"},"content":{"rendered":"

rajeshkumar created the topic: Basic Perforce Administration<\/strong>
\nBasic Perforce Administration<\/p>\n

A. User maintenance tasks<\/p>\n

1. Resetting passwords
\n2. Creating users \/ Deleting users \/ Setting user access
\n3. Disabling the automatic creation of users
\n4. Cleaning up files left open by former users<\/p>\n

B. Administrative operations<\/p>\n

1. Setting the server security level
\n2. Obliterating files to reclaim disk space
\n3. Editing submitted changelists
\n4. Verifying server integrity
\n5. Defining files types to control Perforce’s file type detection mechanism
\n6. Use of the -f flag to force operation<\/p>\n

In perforce, There are 2 Types of authentication menthods.
\n1. passwords
\n2. tickets<\/p>\n

Login to Perforce
\np4 login<\/p>\n

Logout to the perforce
\np4 logout<\/p>\n

Server security levels<\/p>\n

Perforce superusers can configure server-wide password usage requirements, password strength enforcement, and supported methods of user\/server authentication by setting
\nthe security counter. To change the security counter, issue the command:
\np4 counter -f security seclevel<\/p>\n

where seclevel is 0, 1, 2, or 3. After setting the counter, stop and restart the server.<\/p>\n

The default security level is 0: passwords are not required, and password strength is not enforced.<\/p>\n

To ensure that all users have passwords, use security level 1. Users of old client programs may still enter weak passwords.<\/p>\n

To ensure that all users have strong passwords, use security level 2.<\/p>\n

To require that all users have strong passwords, and to require the use of session-based authentication, use security level 3 and current Perforce client software.<\/p>\n

Resetting user passwords
\np4 passwd username<\/p>\n

Creating users
\np4 user -f username<\/p>\n

Preventing creation of users<\/p>\n

1. Create a New p4 group or existing groups
\np4 group p4users
\n2. Set P4 access to that Groups using
\np4 protect
\nand add following..
\nwrite group p4users * \/\/…<\/p>\n

Deleting obsolete users
\np4 user -d -f username<\/p>\n

Reverting files left open by obsolete users<\/p>\n

For example, if the output of p4 opened shows:
\n\/\/depot\/main\/code\/file.c#8 – edit default change (txt) by jim@stlouis
\nyou can delete the “stlouis” client workspace specification with:
\np4 client -d -f stlouis
\nDeleting a client workspace specification automatically reverts all files opened in that workspace, and also removes that workspace\u2019s \u201chave list\u201d.<\/p>\n

Running from inetd on UNIX<\/p>\n

To have p4d start up only when connections are
\nmade to it, using inetd and p4d -i, add the following line to \/etc\/inetd.conf:<\/p>\n

p4dservice stream tcp nowait username \/usr\/local\/bin\/p4d p4d -i -rp4droot<\/p>\n

and add the following to \/etc\/services:<\/p>\n

p4dservice nnnn\/tcp<\/p>\n

where:
\n–> p4dservice is the service name you choose for this Perforce server
\n–> \/usr\/local\/bin is the directory holding your p4d binary
\n–> p4droot is the root directory (P4DROOT) to use for this Perforce server (for example, \/usr\/local\/p4d)
\n–> username is the UNIX user name to use for running this Perforce server
\n–> nnnn is the port number for this Perforce server to use
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n

rajeshkumar replied the topic: Re: Basic Perforce Administration<\/strong>
\nReference links can be found here…<\/p>\n

community.scmgalaxy.com\/pg\/blog\/rajeshku…force-administration
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

rajeshkumar created the topic: Basic Perforce Administration Basic Perforce Administration A. User maintenance tasks 1. Resetting passwords 2. Creating users \/ Deleting users \/ Setting user access 3. Disabling the… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[370],"tags":[373],"class_list":["post-1718","post","type-post","status-publish","format-standard","hentry","category-perforce","tag-perforce"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1718","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=1718"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1718\/revisions"}],"predecessor-version":[{"id":1719,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1718\/revisions\/1719"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=1718"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=1718"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=1718"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}