> As a matter of fact, it can tell. Each server has an identifier > (UUID), and registers its addresses with the VLDB on every startup. > So, if all you are doing is renumbering an existing server, just change > the address and restart it - the rest will happen automatically.
Except in this case, this procedure resulted in both the new and the old
address in the VLDB.
> The problems occur when you use 'vos changeaddr' inappropriately, or if
I never used vos changeaddr. Not even after things were messed up.
> the VLDB already thinks there is a server at the new address. In the
> latter case, it won't let the fileserver register the new address,
> because it belongs to some other server. In current versions of
Hmm. This might be it: the new address never showed up in VLDB, even
though bos showed them running normally. I wonder, how did this happen,
since the fileserver at the old address was stopped before the address
was changed. Shouldn't that be enough? As per IBM docs, it should.
-Juha
--
-----------------------------------------------
| Juha Jäykkä, [EMAIL PROTECTED] |
| home: http://www.utu.fi/~juolja/ |
-----------------------------------------------
signature.asc
Description: PGP signature
