Find the Best Cosmetic Hospitals

Explore trusted cosmetic hospitals and make a confident choice for your transformation.

“Invest in yourself — your confidence is always worth it.”

Explore Cosmetic Hospitals

Start your journey today — compare options in one place.

Basic Perforce Administration

A. User maintenance tasks

1. Resetting passwords
2. Creating users / Deleting users / Setting user access
3. Disabling the automatic creation of users
4. Cleaning up files left open by former users

B. Administrative operations

1. Setting the server security level
2. Obliterating files to reclaim disk space
3. Editing submitted changelists
4. Verifying server integrity
5. Defining files types to control Perforce’s file type detection mechanism
6. Use of the -f flag to force operation

In perforce, There are 2 Types of authentication menthods.
1. passwords
2. tickets

Login to Perforce
> p4 login

Logout to the perforce
> p4 logout

Server security levels

Perforce superusers can configure server-wide password usage requirements, password strength enforcement, and supported methods of user/server authentication by setting
the security counter. To change the security counter, issue the command:

> p4 counter -f security seclevel

where seclevel is 0, 1, 2, or 3. After setting the counter, stop and restart the server.

  • The default security level is 0: passwords are not required, and password strength is not enforced.
  • To ensure that all users have passwords, use security level 1. Users of old client programs may still enter weak passwords.
  • To ensure that all users have strong passwords, use security level 2.
  • 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.

Resetting user passwords

> p4 passwd username

Creating users

> p4 user -f username

Preventing creation of users

1. Create a New p4 group or existing groups
> p4 group p4users
2. Set P4 access to that Groups using
> p4 protect
and add following..
write group p4users * //…

Deleting obsolete users
> p4 user -d -f username

Reverting files left open by obsolete users

For example, if the output of p4 opened shows:
//depot/main/code/file.c#8 – edit default change (txt) by jim@stlouis
you can delete the “stlouis” client workspace specification with:
> p4 client -d -f stlouis
Deleting a client workspace specification automatically reverts all files opened in that workspace, and also removes that workspace’s “have list”.

Running from inetd on UNIX

To have p4d start up only when connections are
made to it, using inetd and p4d -i, add the following line to /etc/inetd.conf:

> p4dservice stream tcp nowait username /usr/local/bin/p4d p4d -i -rp4droot

and add the following to /etc/services:

> p4dservice nnnn/tcp

where:
–> p4dservice is the service name you choose for this Perforce server
–> /usr/local/bin is the directory holding your p4d binary
–> p4droot is the root directory (P4DROOT) to use for this Perforce server (for example, /usr/local/p4d)
–> username is the UNIX user name to use for running this Perforce server
–> nnnn is the port number for this Perforce server to use

Find Trusted Cardiac Hospitals

Compare heart hospitals by city and services — all in one place.

Explore Hospitals
MotoShare.in delivers cost-effective bike rental solutions, empowering users to save on transportation while enjoying reliable two-wheelers. Ideal for city commutes, sightseeing, or adventure rides.

Related Posts

Perforce 2014 Server Upgrade Runbook: Verify, Checkpoint, Restore, and Validate

This guide converts the original Perforce 2014 upgrade notes into a practical runbook for production admins. It covers pre-checks, checkpoint-based recovery, post-upgrade verification, and migration cautions.

Read More

Perforce Server Disk Cleanup and Repository Size Management: A Safe, Practical Playbook

Running out of storage on a Perforce (Helix Core) server can quickly become an availability risk. This guide shows a safer cleanup workflow: measure space first, compare options, then execute changes with minimal operational risk.

Read More

Perforce Interview Prep: Essential p4 Commands for Workspaces, Changelists, and Admin Tasks

A practical Perforce interview refresher focused on high-value commands and admin concepts from real usage. Learn how to query changelists, exclude files, use metadata options, and avoid risky data-removal mistakes.

Read More

Perforce Training Guide: Hands-On P4 Curriculum for Users, SCM Engineers, and Release Teams

This revised guide turns a legacy Perforce training announcement into a practical reference for planning team enablement. It summarizes the syllabus, lab workflow, core P4 command areas, and post-training adoption practices.

Read More

Perforce Backup Commands: Checkpoints, Journal Rotation, and Restore Workflow

This guide explains the core Perforce backup commands from the original post and how to use them in a practical backup and restore workflow. You will get a command reference, comparison tables, and ready-to-adapt examples.

Read More

Perforce Tools Explained: Clients, Servers, Plug-ins, and Utilities (Legacy 2012 Reference)

This updated reference explains the Perforce tools listed in the original 2012 post, what each component does, and how they fit together. It also includes a practical p4 CLI workflow and cautions for legacy or renamed components.

Read More
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
0
Would love your thoughts, please comment.x
()
x