[p4] Checkpoint hung, tables locked? ... support not in yet

Dan Wierenga dwierenga at valueclick.com
Wed Apr 2 09:00:22 PDT 2008


Checkpoints don't really produce any output between the very start and
the very end (I've got an enhancement request to give some kind of
status output, actually).  So it may very well not be "hung".  I would
really, really recommend against killing a checkpoint though.

Incidentally, the UK and Australian offices are willing to help US
customers during their office hours, which amounts to Support being open
much "earlier" than you'd think.  :D

> -----Original Message-----
> From: perforce-user-bounces at perforce.com [mailto:perforce-user-
> bounces at perforce.com] On Behalf Of Ed Mack
> Sent: Wednesday, April 02, 2008 7:25 AM
> To: perforce-user at perforce.com
> Subject: [p4] Checkpoint hung, tables locked? ... support not in yet
> 
> We have a situation where our checkpoint is hung.  There is no
> checkpoint output, though our captured stdout says that the checkpoint
> has begun.  A "p4 info" doesn't come back.
> 
> Has anyone else run into this?  I am wondering if we can safely kill
> the
> process(es) and be okay.  Will the tables be locked?
> 
> Thanks,
> Ed
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user



More information about the perforce-user mailing list