Renà Berber wrote:
> On 6/15/2016 7:42 PM, Bill Zissimopoulos wrote:
> > (1) Is my assumption that Windows heaps are not properly cloned after a
> > fork correct? A 2011 post [2] seems to suggest so.
> > (2) Is there any workaround that the WinFsp DLL can use to get around
>this
> > limitation an
On 6/15/2016 7:42 PM, Bill Zissimopoulos wrote:
[snip]
> WinFsp consists of an FSD (file system driver) and a DLL component. The
> WinFsp DLL uses the Windows heap functions to manage memory
> (HeapAlloc/HeapFree). It seems that the Windows heap is not properly
> cloned after a fork, which leads t
I am the creator of WinFsp [1], a user mode file system solution for
Windows (i.e. FUSE for Windows). WinFsp has its own API, but I have been
working on adding a FUSE (high-level) API using SSHFS as my primary test
case. This has proven to work very well, except for one important problem
which is t
Achim Gratz writes:
> Due to a problem during upload, these packages have been re-released as
> *-2 and the previous *-1 release has been removed:
>
> perl-Business-ISBN-2.011-2
> perl-Mojolicious-6.64-2
> perl-Regexp-Common-2016060801-2
> perl-XML-LibXML-2.0125-2
Also affected by this problem and
4 matches
Mail list logo
