12 messages in com.perforce.perforce-user[p4] Tips to set up user accounts.
FromSent OnAttachments
Kalapatapu, Pallavi19 Jun 2001 12:19 
Chuck Karish19 Jun 2001 13:33 
Stephen Vance19 Jun 2001 14:13 
Thom...@sybase.com19 Jun 2001 15:16 
Kalapatapu, Pallavi19 Jun 2001 15:27 
Chuck Karish19 Jun 2001 16:31 
Stephen Vance19 Jun 2001 19:54 
Schaible, Jorg20 Jun 2001 00:41 
"Schaible, Jörg"20 Jun 2001 02:59 
"Schaible, Jörg"20 Jun 2001 02:59 
Stephen Vance20 Jun 2001 07:56 
Schaible, Jorg20 Jun 2001 08:28 
Subject:[p4] Tips to set up user accounts.
From:"Schaible, Jörg" (Joer@gft.com)
Date:06/20/2001 02:59:46 AM
List:com.perforce.perforce-user

Hi,

Paul has given another very valuable solution for this access right deadlock situation, but he missed the cc for the list:

From: Paul Goffin [mailto:PGoffin at baltimore.com]

Sent: Wednesday, June 20, 2001 10:48 AM To: Schaible, J?rg Subject: RE: [p4] Tips to set up user accounts.

[snip]

FYI - it's not the only way. (But the other way certainly isn't for beginners!)

The "Other way":

1. Take a checkpoint (anyone can do this).

2. "grep" for the "db.protect" records.

3. Find all records that are restricting your "super" access rights.

4. Working on a copy of those records, substitute the "@pv@" at the beginning of the offending lines with "@dv@".

Save that copy (to a file)

5. "recover" the "@dv@" records into the server (p4d -jr "filename").

You DO NOT have to stop the server to do this.

6. You can now run "p4 protect".

Like I said, not for beginners...

Paul.

Thanks. Paul, this was really interesting. While I have really some experience in modifying checkpoints and journals, I never recognized the @dv@ lines. Just curious, what does it mean exaclty?

Greetings, J?rg

BTW: Has anyone ever tried the Berkley DB support of MySQL to access the db.* files of Perforce? It is just an idea, but I had never the time ...