[p4] How can I tell which machine a p4d process is talking to?
dfogleso at adobe.com
Mon Dec 17 15:22:05 PST 2001
The only way to audit user commands is to run with the server debug flag
(-v). This will send output to the file sepecified with the log (-L) flag.
-v1 will give you information about what user, client, IP issued the
command, and the PID for the process.
If you're running 2001.1, use -v2 instead, since that will give you when the
completed, which can sometimes be useful information.
There are varying levels of verbosity to the debug output, but rarely will
you need anything higher than -v2.
Once you see a child process that is eating up CPU/RAM, you can tail the log
file and find the PID to identify the user/command that is the cause.
----- Original Message -----
From: "Karl Elvis MacRae" <kmac at apple.com>
To: <perforce-user at perforce.com>
Sent: Monday, December 17, 2001 2:57 PM
Subject: [p4] How can I tell which machine a p4d process is talking to?
> Once in a while I have a user do something disruptive like
> delete a depot in the middle of the day (which seems to hang
> perforce until the delete completes). I see, on my Solaris perforce
> the p4d processes backing up while waiting for the server to respond.
> But I can't tell, when this is happening, what host the hang is coming
> So I can't tell who's issued a p4 depot -d (or whatever the command was).
> Is there any way to identify which process is talking to which host?
> If I can identify which host, I can track it to a user running a command
> that may be hanging things up.
> Karl Elvis MacRae VLSI CAD Apple Computer kmac at apple.com
> 408-974-0847 (voice) 408-313-5741 (cell)
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user