From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.dk
Subject: Re: autoloading from deleted wordcode digest files
Date: Wed, 6 Jun 2001 10:44:39 +0000 [thread overview]
Message-ID: <1010606104439.ZM1317@candle.brasslantern.com> (raw)
In-Reply-To: <200106060947.LAA23791@beta.informatik.hu-berlin.de>
On Jun 6, 11:47am, Sven Wischnowsky wrote:
} Subject: Re: autoloading from deleted wordcode digest files
}
} 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).
The OS does ensure that they're not deleted -- it keeps the inode around
but deletes the directory entry, just as for any other open file (cygwin
notwithstanding); but autoloading checks for the existence of the file by
name before using the already-mapped copy. Clint wants zsh to remember
what name it used to map a file and then keep using that mapped copy even
after the name has gone away on disk.
} 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?
You have it backwards. Clint wants check_dump_file() to search for a
function in the already-mapped files because load_dump_header() fails
if it can't do an open().
} > Will this break anything?
}
} This certainly depends on how you write it ;-) And probably on the way
} the system handles all this.
The problem I see with it is that it could cause mysterious violations
of fpath ordering. I guess it wouldn't be so bad if it were only the
fallback case exactly when load_dump_header() can't open().
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-06 10:46 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
2001-06-06 10:44 ` Bart Schaefer [this message]
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=1010606104439.ZM1317@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).