From: Mike Eisler (mre@eng.sun.com)
Date: 03/18/99-02:35:05 PM Z
Date: Thu, 18 Mar 1999 12:35:05 -0800 (PST) From: Mike Eisler <mre@eng.sun.com> Subject: Re: Remapping files - up-reving discussion Message-ID: <Roam.SIMC.2.0.6.921789305.19874.mre@eng.sun.com> > But even for "read-only" file systems, this is an issue - eventually > software gets updated... If the update is done by overwriting the existing file it doesn't matter if fh's are preserved or not. Stuff breaks. > What are the solutions here? Is this considered a killer issue? > What is Sun's experience here? Sun has lots of shared software stored in read-only NFS replicas. Our experience is quite good. Even if software gets updated, because the software is updated such that the executable file in the bin directory is a symlink to say file,v1.1, changing the symlink affects only new executions of the software. Software that is currently executing doesn't get affected, until the version is obsoleted, and deleted from the server. Because the automounter maps already supported replica syntax, when clients upgraded to Solaris 2.5, they didn't really notice anything, except that when their software server went down, things still worked. -mre
This archive was generated by hypermail 2.1.2 : 03/04/05-01:46:52 AM Z CST