[p4] monitoring the perforce server?

[Jeff Grills]

The only thing else I could think of that might be a really good candidate
as far as no table locking is concerned would be "p4 help", since help text
is stored on the server.  I still think "p4 info" is better, though.  Taking
a table lock might not be a bad idea to know if the server is somewhat
functional, as it would test some disk access from the p4 server as well.
 
j

-----Original Message-----
From: Stephen Vance [mailto:steve at vance.com] 
Sent: Saturday, October 28, 2006 10:38 AM
To: Mike
Cc: Jeff Grills; perforce-user at perforce.com
Subject: Re: [p4] monitoring the perforce server?


Even the API doesn't give you any finer grained access than the
sub-commands. I would simply use 'p4 info' for this purpose, as it is one of
the few (the only?) commands that connects to the server without locking any
database tables.

Steve

Mike wrote: 

On Fri, 27 Oct 2006, Jeff Grills might have said:



  

Executing 'p4 info' would do the task if 'p4' were on every platform.

      

'p4' and its kind are the only things you can safely use to connect to a

perforce server, unless you build your own application built against the

p4api library.  What else were you thinking might be possible?  I don't

think the on-wire protocol is officially documented anywhere if you were

wanting to just send it some packets.

    



I am hoping to find that I can safely connect then issue a 'quit' for the

server to break the connection.



Mike

_______________________________________________

perforce-user mailing list  -  perforce-user at perforce.com

http://maillist.perforce.com/mailman/listinfo/perforce-user