Re: [p4] p4 monitor terminate never seems to work
Matt Janulewicz <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'Matt Janulewicz'. [https://forums.perforce.com/index.php?app=forums&module=forums§ion=findpost&pid=22495] Miles O, on 2017/10/16 16:10:52 UTC, said: > FWIW: We don't have to run terminate too often, but I find that at least half the time, I end up having to kill the process on the server. I don't have any data on which commands cause this. I've seen this since I started working with Perforce, including 2013.x, 2015.x or 2016.x, and 2017.1 . > I find that I have to do a proper 'kill' 100% of the time. My usual process is 'p4 monitor terminate pid', 'p4 monitor clear pid', 'kill pid'. I also find that on our Commit server we typically have around 100 pid's active (ps ax | grep p4d), though 'p4 monitor show' usually only shows about 10-15 processes, what I'd expect. I think perhaps when people 'ctl+c' on a process it doesn't get killed on the server. I long ago accepted this as a fact of life. -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/3581-p4-monitor-terminate-never-seems-to-work _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user