Mail Archives: djgpp-workers/2000/11/20/01:45:31
On Sun, 19 Nov 2000, Peter J. Farley III wrote:
> In further researching the F_GETLK fcntl function, I see that Mark E.'s
> comment in his fcntl source that the int21/5C interface does not return
> information on what lock prevented this request is true, at least
> according to the Ralf Brown list.
Please tell why do you need this. Is it for filling the `flock'
structure in response to the F_GETLK request?
If so, then I think the only way to supply the info would be to store
the information from F_SETLK (and flock/lockf, when we have them)
internally. Do you see any problems with this approach in the context
of intended usage of these functions within Perl?
> I assume that the W9x and NT/2K replacement for SHARE.EXE, the
> IFSManager, has equivalent functions and data structures.
The Windows replacement for SHARE.EXE is VSHARE, not IFSMgr.
As for the internat data structures, there should be equivalent data
structures, but I won't bet on them being similar.
> Q1: Is there any doc (outside of a developer non-disclosure agreement
> with M$) on the API to the IFSManager locking functions?
You could try searching RBIL for VSHARE.
> Q2: If someone already knows about this API, is it worth our time
> trying to investigate it?
I don't think so. Locking support seems pretty much of marginal
importance in DJGPP (we've managed without it until now, didn't we?),
so I'd say maintaining the locking records inside the current program
is enough. If we need to share this infor between different programs
running on Windows, we could devise some disk-based solution.
- Raw text -