mailing list of musl libc
 help / color / mirror / code / Atom feed
From: boris brezillon <b.brezillon.musl@gmail.com>
To: musl@lists.openwall.com
Subject: Re: ldso: dlclose.
Date: Sat, 25 Aug 2012 09:54:23 +0200	[thread overview]
Message-ID: <CAKAk8dYJ9pSg9G+CC2=y=3CZbiSHh=GvmvX5t0E6nRJ8+Y=4cg@mail.gmail.com> (raw)
In-Reply-To: <20120824174640.GD27715@brightrain.aerifal.cx>

2012/8/24 Rich Felker <dalias@aerifal.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


      reply	other threads:[~2012-08-25  7:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19 16:26 musl
2012-08-20  0:48 ` Rich Felker
2012-08-22 22:41   ` Rich Felker
2012-08-23 12:39   ` Arvid E. Picciani
2012-08-23 12:48     ` Rich Felker
2012-08-23 16:02       ` orc
2012-08-23 18:01         ` Rich Felker
2012-08-24  7:52           ` musl
2012-08-24 12:27             ` Rich Felker
2012-08-24 13:54               ` musl
2012-08-24 17:46                 ` Rich Felker
2012-08-25  7:54                   ` boris brezillon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKAk8dYJ9pSg9G+CC2=y=3CZbiSHh=GvmvX5t0E6nRJ8+Y=4cg@mail.gmail.com' \
    --to=b.brezillon.musl@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).