Date: Sat, 25 Aug 2012 09:54:23 +0200 From: boris brezillon <b.brezillon.musl@...il.com> To: musl@...ts.openwall.com Subject: Re: ldso: dlclose. 2012/8/24 Rich Felker <dalias@...ifal.cx>: > On Fri, Aug 24, 2012 at 03:54:25PM +0200, musl wrote: >> I was talking about this specific case : >> 1) unloding a plugin >> 2) updating the plugin (new plugin.so) >> 3) reloading the plugin >> >> During the whole sequence the application is up and running. >> >> Here is how I should do it if dlclose is implemented per posix : >> 1) stop the application >> 2) update the plugin >> 3) restart the application > > To clarify on "per POSIX", POSIX allows but does not require dlclose > on the last reference to remove the library from the process's address > space, but requires that this not happen if the library has been used > to resolve undefined symbols. > >> The application is not available during this sequence. > > If the application just re-execs itself rather than exiting, there is > no window during which it's unavailable. See how irssi handles the > /upgrade command for an example. That might be the cleanest way to > handle what you want to do. > This sounds interesting, I'll take a look. > Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.