[p4] P4 monitor show
G Barthelemy
gb.perforce at googlemail.com
Fri Jan 5 15:40:27 PST 2007
On 1/5/07, Jamie.Echlin at barclayscapital.com
<Jamie.Echlin at barclayscapital.com> wrote:
> I appreciate that, but it doesn't get round the fact that the monitor
> command can fail to run wherever it is run, even if it's only run once
> every 3 seconds even if a hundred people are viewing the page.
Could an alternative approach be to parse p4d's error log on the
server, assuming you have debug set to at least "server=2" which would
give you the completion time for each command?
Sure it would be more involved than monitoring the output of "monitor
show" as you would need to remember what command has been started when
(and from time to time check that the PID is still in the process
table as commands can be aborted without a completion being logged),
but all in all this could be a way of monitoring your Perforce server
activity in real time, without having to resort to run p4 commands,
making for a less intrusive or expensive method.
If your log was written to a volume that's mounted from another
machine, or rsync'd to another machine, you could even process it away
from your production server, and therefore with very little CPU cost.
--
Guillaume Barthelemy
More information about the perforce-user
mailing list