Safe updating of shared libs/binaries
Eric A. Pearce
eap at bu-it.bu.edu
Mon Apr 29 05:20:00 AEST 1991
I'm interested in hearing how other people deal with the problem of
updating shared libraries and executables under SunOS. The usual result
of just overwriting a running executable or library is that your programs
dies in a big way. This is pretty disruptive if it's your X server.
Our current level of automation is to run "rdist" and use the "special"
feature, i.e.
special /usr/lib/lib*X* "/usr/etc/ldconfig" ;
But this really doesn't do much for the crashing problem. I suppose you
could "mv" the running binary to a new location, copy in the new
executable and remove the old after a certain grace period. Would you
want setuid programs scooting around in other directories anyways? This
doesn't make much sense for a shared library (as I understand it) since
the location is set in the cache.
Does anybody have a "clean" solution to this problem?
Eric Pearce eap at bu-it.bu.edu
More information about the Comp.sys.sun
mailing list