[p4] What happen when P4D is stopped

[Robert Cowham]

> 
> You should only have a single p4d for a particular Perforce root!  
> "p4d" will spawn other 'p4d' daemons as necessary, but these 
> are all child tasks of the first, and that first p4d has 
> control of the database. Multiple 'p4d' tasks you spawn 
> yourself can corrupt the database. I am not even sure 
> Perforce allows this because I've never even tried it.

Interestingly I have seen occasions where more than one p4d use the same
root, so it isn't a total no-no.

Anyone doing this on their live server?

One trick is for example to have a separate (dummy) database with a single
table, e.g. db.monitor, linked to the "live" copy.

Robert