[p4] What happen when P4D is stopped

[Pankaj Gupta]

Thanks for the detailed answer.
  Please give further details on:
   
  - all client transition is comepleted ? what kind of transition is done.

  - all client connections to the server is terminated, if a submit huge is going on would that be stopped in between ? If there is a integ running which is going to take another an hour or so..
   
   
  Does P4 writes anywhere in the database that it is killed? Imagine a scnerio where two P4D are running using same root.. and one is stopped what will be the behaviour of the other one?
   
  ---
  
David Weintraub <qazwart at gmail.com> wrote:
  If p4d is stopped by the "p4 admin stop" command or by doing a "kill
-15", all client transactions are completed, the journal file is
closed, and all client connections to the server are terminated. That
way, when you bring p4d back up, you simply continue where you left
off. If p4d is brought down hard (that is, you do a "kill -9" or
simply unplug the server, there might be a possibility that not all
transactions were completed. However, Perforce seems pretty good and
determining the last valid state of the Perforce universe and is able
to pick things up from where they left off. You might have to rebuild
the database from the checkpoint file, but otherwise there usually
isn't too many problems.

Not too sure what you were asking. Are you talking about what the
developers do when the p4d process is stopped? Developers certainly
cannot create a new client, or sync the files when p4d is stopped, but
they can work on the files currently residing in their clients by
turning off the "read only" flag in Windows or by turning on the write
bit in Unix.

Once p4d is back up and running, the developers can sync their views
back to the server using the "p4 diff" command to find files they
deleted, edited, and added to their clients, and by running the "p4
edit", "p4 delete", or "p4 add" commands to sync their view back up.
One of the complaints about Perforce is that this isn't as automated
step as it should be. However, I believe that P4V and p4win have a
menu selection that does this, and it isn't too difficult to write a
shell script to do this from the command line.

You can look at the "Working Detached" section in Chapter 4 Managing
Changelists and Files in the Perforce User Guide

or Tech Note #2
. For a more
detailed explanation.

I hope that answers your question.

On 3/23/07, Pankaj Gupta wrote:
> Hi,
>
> I want to know the steps happen at low level when a P4D is stopped.
>
> Thanks for the help,
>
> Amit
>
>
> ---------------------------------
> Get your own web address.
> Have a HUGE year through Yahoo! Small Business.
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
--
David Weintraub
qazwart at gmail.com


 
---------------------------------
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.