Re: GDBM 1.11, 1.13 incorrectly handle gdbm_reorganize() if filesystem is NFS
Bob Proulx <[email protected]> Thu, 22 Jun 2017 22:35:12 -0600
| Newsgroups | gmane.comp.gnu.utils.bugs |
|---|---|
| Message-ID | <[email protected]> |
Hello Sebastian, Sebastian Gniazdowski wrote: > I'm using new (not yet merged) gdbm Zsh module. It maps shell's hash > table onto GDBM. Current Zsh upstream has previous version, but it > behaves the same. I am not sure if you are having trouble with zsh or with gdbm. However this mailing list isn't very active as you can see from the archives of it. https://lists.gnu.org/archive/html/bug-gnu-utils/ I don't know if you will get a response from anyone on whichever question you are asking. > even after "unbind" done in Zsh. I've checked that the unbind > correctly calls gdbm_close(). > > Commenting-out gdbm_reorganize() call fixes this. This is a proof > that gdbm_close() is really called, 100% of problem lies in > gdbm_reorganize(). > > So basically the error is: > > - with NFS file-system, gdbm_reorganize() harms GDBM_FILE structure > - so that gdbm_close() doesn't release the database, and it's > - impossible to connect to the database again, if no restart of > - shell. It seems like you are having a zsh problem with zsh using gdbm? In which case I suggest reporting this to a zsh specific list. However I notice that you are already known there. If you are thinking this is a bug in gdbm then please report it to the gdbm folks. The docs give this: "Once you’ve got a precise problem, send e-mail to [email protected]." This is probably all of the help we can give you here on bug-gnu-utils. Good luck! Bob