15 messages in com.perforce.perforce-user[p4] Recursive List of Depot - Direct...| From | Sent On | Attachments |
|---|---|---|
| Fawad Khan | 21 Aug 2002 15:56 | |
| Stephen Vance | 21 Aug 2002 18:33 | |
| Dave Tuttle | 23 Aug 2002 13:51 | |
| Jim Hanrahan | 23 Aug 2002 14:33 | |
| Chuck Soper | 23 Aug 2002 15:02 | |
| Justin Hahn | 23 Aug 2002 15:32 | |
| Arnt Gulbrandsen | 23 Aug 2002 15:36 | |
| Jason Williams | 23 Aug 2002 15:42 | |
| Robert Cowham | 23 Aug 2002 15:53 | |
| Jim Hanrahan | 23 Aug 2002 16:04 | |
| Matthew Rice | 23 Aug 2002 17:15 | |
| Arnt Gulbrandsen | 23 Aug 2002 21:41 | |
| Matthew Rice | 24 Aug 2002 06:16 | |
| John Marshall | 24 Aug 2002 07:14 | |
| Jason Williams | 26 Aug 2002 10:43 |
| Subject: | [p4] Recursive List of Depot - Directories only |
|---|---|
| From: | Jason Williams (str...@narus.com) |
| Date: | 08/26/2002 10:43:22 AM |
| List: | com.perforce.perforce-user |
If I remember correctly, "p4 dirs" was an unsupported command for awhile. One of the reasons I thought it was unsupported was because of the load it drew on the server. A later release seemed to have fixed the performance issues (With hundreds of P4Win clients pegging the server with "p4 dirs", I can see how it would drain the resources of the server).
I do think this has been fixed though.
--Jason
-----Original Message----- From: John Marshall To: Jason Williams Cc: j.hanrahan at advantest-ard.com; perforce-user at perforce.com Sent: 8/24/02 7:14 AM Subject: Re: [p4] Recursive List of Depot - Directories only
On Fri, Aug 23, 2002 at 03:42:26PM -0700, Jason Williams wrote:
I'm not sure which shells are available on Windows, but a simple sh/bash script like this seems to work like a charm:
#!/bin/sh [does lots of "p4 dirs <foo>" commands]
This is going to sound a little bit FUDish. I no longer have access to (the old version of) this script, and I don't remember what p4d version it was -- but it was probably 1999.2 or so, so this concern might no longer be relevant.
In a previous life I had a script that did "p4 dirs" commands recursively in a tight loop like this. It worked very nicely every time when I was testing it at 3am.
If I used it during the day, when some proportion of the ~300 users were also making requests of the server at the same time, it would usually lock up the server; after a minute I'd kill the script (to no avail), and after twenty minutes we'd restart the server and glare at John very hard.