From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: autoloading from deleted wordcode digest files
Date: Wed, 6 Jun 2001 11:47:26 +0200 (MET DST) [thread overview]
Message-ID: <200106060947.LAA23791@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <20010603124544.A27964@dman.com>
Clint Adams wrote:
> I'm making .zwc files using zcompile -U -M.
> zsh will keep these files opened and mmapped even
> after they are deleted, but efforts to autoload
> functions within will fail.
>
> I want the deleted file to be searched if the function
> is not found on disk. I assume that this can be accomplished
> by including the filename in struct funcdump, and using
> that as an identifier should the files be deleted after
> mmapping.
Somehow I think the OS should ensure that such files can't be deleted
(by renaming them as it does for the .nfs* files or something).
Hm, things could break terribly if mapped function files disappear and I
don't see a completely satisfying solution. Searching again for the zwc
file works for functions that haven't been loaded yet, but what about
those that were used already?
> Will this break anything?
This certainly depends on how you write it ;-) And probably on the way
the system handles all this.
My first reaction would be to print a warning, suggesting to re-start
the shell and mark the funcdump structure to not be used again. But
that's only one step back from re-searching and -opening it, as you
suggest.
In short: hm, shrug, dunno.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-06-06 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-03 16:45 Clint Adams
2001-06-06 9:47 ` Sven Wischnowsky [this message]
2001-06-06 10:44 ` Bart Schaefer
2001-06-06 11:14 ` Sven Wischnowsky
2001-06-06 11:21 ` Andrej Borsenkow
2001-06-06 14:25 ` Clint Adams
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=200106060947.LAA23791@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.dk \
/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/zsh/
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).