Changing hostname

[Frederic Praca]

Hello guys,
I finally repaired my coda file system thanks to this mail
(http://www.coda.cs.cmu.edu/maillists/codalist/codalist-2006/7900.html ).

Now, I'm looking for a safe way to change the hostname of the server the
SCM is running on.
Is there a way to change it without re-installing
the whole SCM ?

I'm pretty sure it exists as Coda never betrayed me :-)

Thanks for help

Fred
--
"... Je me suis imposé la loi de ne procéder jamais que du connu
à l'inconnu, de ne déduire aucune conséquence qui ne dérive
immédiatement des expériences et des observations ..."
        -+- Antoine-Laurent Lavoisier, 1743-1794 -+-

[Jan Harkes]

Frederic Praca wrote:
> Hello guys,
> I finally repaired my coda file system thanks to this mail
> (http://www.coda.cs.cmu.edu/maillists/codalist/codalist-2006/7900.html ).
>
> Now, I'm looking for a safe way to change the hostname of the server the
> SCM is running on.
>  
I guess this name change implies an ip-address change as well. Changing
the name isn't that hard, just edit the /vice/db/servers file on the SCM
and /vice/db/hostname on the server whose name is changing. If the name
of the SCM changes, you also need to update /vice/srv/scm.

After editing these files the changes should automatically propagate to
all servers, if that isn't happening, restart the update daemons. Then
restart the Coda servers, the name-to-address resolution only happens at
startup, so they won't pick up the new server address until all of them
have been restarted.

Finally (the most painful part) all clients need to be reinitialized,
otherwise even if they successfully pick up the new addresses they will
keep trying to reconnect to the old server address.

Jan

[Frederic Praca]

Le Sat, 10 Oct 2009 00:27:21 -0400,
Jan Harkes <jaharkes@...> a écrit :

> Frederic Praca wrote:
> > Hello guys,
> > I finally repaired my coda file system thanks to this mail
> > (http://www.coda.cs.cmu.edu/maillists/codalist/codalist-2006/7900.html ).
> >
> > Now, I'm looking for a safe way to change the hostname of the
> > server the SCM is running on.
> >  
> I guess this name change implies an ip-address change as well.
No, in fact, it's only a problem with my sendmail configuration which
forces me to change my hostname to a public FQDN.

> Changing the name isn't that hard, just edit the /vice/db/servers
> file on the SCM and /vice/db/hostname on the server whose name is
> changing. If the name of the SCM changes, you also need to
> update /vice/srv/scm.
>
> After editing these files the changes should automatically propagate
> to all servers, if that isn't happening, restart the update daemons.
> Then restart the Coda servers, the name-to-address resolution only
> happens at startup, so they won't pick up the new server address
> until all of them have been restarted.

That's what I've done last time I tried.
 
> Finally (the most painful part) all clients need to be reinitialized,
> otherwise even if they successfully pick up the new addresses they
> will keep trying to reconnect to the old server address.
Aha, forgot that last time, that could explain a lot of problems I got.

Now it works, thanks for help
 
> Jan
Fred