Rather than newest last write time of all dlls loaded, use the forking
process' windows pid and windows thread id as directory name to create
the forkable hardlinks into. While this may create hardlinks more
often, it does avoid conflicts between dlls not having the newest last
write time.
---
wi
On Apr 12 15:32, Michael Haubenwallner wrote:
> Rather than newest last write time of all dlls loaded, use the forking
> process' windows pid and windows thread id as directory name to create
> the forkable hardlinks into. While this may create hardlinks more
> often, it does avoid conflicts betwe
Corinna Vinschen writes:
> On Apr 12 15:32, Michael Haubenwallner wrote:
>> Rather than newest last write time of all dlls loaded, use the forking
>> process' windows pid and windows thread id as directory name to create
>> the forkable hardlinks into. While this may create hardlinks more
>> often
On 4/13/19 9:36 AM, Achim Gratz wrote:
> Corinna Vinschen writes:
>> On Apr 12 15:32, Michael Haubenwallner wrote:
>>> Rather than newest last write time of all dlls loaded, use the forking
>>> process' windows pid and windows thread id as directory name to create
>>> the forkable hardlinks into.
