At 8:06 PM -0400 4/16/01, David E. Cross wrote:
[...skipping over some important stuff...]
>My second solution was to have the child call yp_init_dbs()
>instead of yp_flush_all() (the former would just nuke the
>references to the FDs, but actually keep them open). This
>didn't work. Can anyone provide any clues as to why? Does
>the DB library keep its own cache, and unless they are
>"really" closed it will just loop back to the open ones anyway?
>The current solution is suboptimal since for many cases it
>removes the DBCACHE entirely, but I don't know what other
>solution exists.
>JKH: I think this _really_ needs to get into 4.3-RELEASE,
>this has been a vexing bug for over a year. The current
>solution may be sub-optimal, but...
I'm inclined to think that we should have a better understanding
of what is going on in the DB routines in this parent/child
situation. If it was something that worked in 4.2 but would
be newly broken in 4.3, then I would be more inclined to see
a last-minute sub-optimal fix rushed into 4.3, but as it is
I do not have a warm fuzzy feeling that the real problem is
understood at this point.
If someone familiar with these DB routines could look into
Dave's problem and comment, that would make any patch feel
somewhat warmer and fuzzier... Perhaps Dave should put up
a proposed patch to the gang in freebsd-audit as well as
freebsd-hackers?
--
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
