[p4] What happen when P4D is stopped

[Jeff Grills]

If you prefer, you can stop the server with a "p4 admin stop" command, which
gives the server the opportunity to nicely shut everything down.  The same
thing likely happens on a TERM signal.  I wouldn't recommend KILL signal
(-9) since you really do want the server to finish writing any delta files,
update the DB files, and close everything down nicely.

>From what I see (at least on a unix server), it looks like perforce runs one
process that listens for incoming connections, forks, and then does all its
real work in the child processes.  Those child processes are going to lock
portions of the DB files, read and write the archive files, etc.  So it's
not just a process, but it's a tree of processes.  And you do want the
children to finish what they're doing.

j


> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Bob Aiello
> Sent: Friday, March 23, 2007 8:53 AM
> To: paul goffin
> Cc: Robert Cowham; Perforce Users Mailing List
> Subject: Re: [p4] What happen when P4D is stopped
> 
> If its just a process then I understand. But most startup and 
> shutdown involves a few more steps. For example a kill -1 
> (via an interupt caught) does cleanup but a kill -9 is 
> immediate. Usually the internals of startup and shutdown are 
> more detailed. But if it is just a process then that is 
> fine... Thanks!