At 03:43 AM 01/11/2000 , Batlin, Alex wrote:
>Does this mean that one should rm .pid when moving the vob to another
>server?
Well, categorically, the PID is meaningful only on the host machine where
it was allocated. This is a UNIX thing, not a ClearCase thing: each
process that the kernel launches is assigned an integer identifier, which
the kernel guarantees will always be unique - but only within the one
machine, and only for the lifetime of the process to whom it's
assigned. The PIDs are recycled when the processes die, and there's
nothing what so ever done to compare, relate, or avoid the PIDs being
assigned on any other machine. You don't give many details on your
"copying" and "contingency" machinery, but whatever it is you're doing, it
should certainly not be expecting the PID to be meaningful on more than one
machine.
Whether that means "remove .pid", or simply "don't expect it to mean
anything" is up to you. I very much doubt that this .pid file "confuses
ClearCase" in any way; it seems to be there only to help you, the
administrator, do the sort of thing you're trying to do (but within the
bounds of a single machine!).
Informix Software, Inc. Jack Repenning
Config/Release Mgmt Jack.Repenning@informix.com
4100 Bohannon Drive M/S: 4100/2
Menlo Park, CA 94025 FAX: 413/832-0743
VOICE: 650/926-1044 PAGE: 800/781-6182
PGP/RSA: D24B E2C2 9AFB 7C24 : 7E59 7885 525D 644E
PGP/DSS: 955C 44AD 8FCE 77D4 9494 \
: 4AB2 51F1 3EED 3B82 E870
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:24 EDT