3 messages in com.perforce.perforce-user[p4] Write-only client spec| From | Sent On | Attachments |
|---|---|---|
| Richard Tomasso | 22 Sep 1999 09:44 | |
| Dave Lewis | 22 Sep 1999 09:58 | |
| Richard Tomasso | 22 Sep 1999 10:03 |
| Subject: | [p4] Write-only client spec![]() |
|---|---|
| From: | Dave Lewis (dle...@vignette.com) |
| Date: | 09/22/1999 09:58:48 AM |
| List: | com.perforce.perforce-user |
From: Richard Tomasso <rtomasso at xionics.com>
> Date: Wed, 22 Sep 1999 12:45:06 -0400 (EDT) > X-Mailer: ELM [version 2.4 PL24] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > Sender: perforce-user-admin at perforce.com > Errors-To: perforce-user-admin at perforce.com > X-Mailman-Version: 1.0rc3 > Precedence: bulk > List-Id: Discuss Perforce with other users <perforce-user.perforce.com> > X-BeenThere: perforce-user at perforce.com > > I've been trying to delete some clients which are no longer used on our > server. The clients belong to an employee who left. The employee had > super privs in the protect table. When I try to edit their clients, the > file always comes up read-only. This hasn't happened before. Any > thoughts on how this situation was created or how to change it? > > > _______________________________________________ > perforce-user mailing list - perforce-user at perforce.com > http://maillist.perforce.com/mailman/listinfo/perforce-user > I've never messed with this. I always just use p4 client -f -d as the perforce super-user. Perhaps you could take away their super privs first?
dave




