[p4] How can I tell which machine a p4d process is talking to?

Chuck Karish karish at well.com
Tue Dec 18 08:02:36 PST 2001

And, of course, the process IDs are also in the p4d log file.  Just match them
up.  I tend to do 'netstat -a | grep 1666' to get a list of candidates.

At 11:22 PM 12/17/2001 -0500, Stephen Vance wrote:
>netstat is the command.  If I remember correctly, -sr is the set of flags to use.  If I got the right ones, it will tell you which PID has which sockets, including the end point IPs and ports.  That way you can find out without the foresight to turn on server verbosity.
>At 02:57 PM 12/17/2001 -0800, Karl Elvis MacRae wrote:
>>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 server,
>>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 from.
>>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
>Stephen Vance
>mailto:steve at vance.com
>perforce-user mailing list  -  perforce-user at perforce.com

Chuck Karish            karish at well.com           (415) 317-0182

More information about the perforce-user mailing list