Re: Thread-safe file locking
Richard <rgrdev@gmail.c omwrote in news:7v642a8l9t .fsf@individual .net:
F'ups: Follow-ups. That particular contraction has been used on USENET
for decades now...
Richard <rgrdev@gmail.c omwrote in news:7v642a8l9t .fsf@individual .net:
CBFalconer <cbfalconer@yah oo.comwrites:
>
>
Really? You must be a hobbyist programmer.
>
I have never heard of "F'ups".
>
>Matt Brandt wrote:
>>
>Both threads and C++ are off-topic here (on c.l.c). We never heard
>of a PID either. F'ups set.
>>>
>>I am trying to get multiple threads to lock specific regions of a
>>file. However, since each thread has the same PID, it appears that
>>a lock by one thread does not block another thread from the same
>>process.
>>>
>>How does one maintain file locking between sibling threads?
>>I am trying to get multiple threads to lock specific regions of a
>>file. However, since each thread has the same PID, it appears that
>>a lock by one thread does not block another thread from the same
>>process.
>>>
>>How does one maintain file locking between sibling threads?
>Both threads and C++ are off-topic here (on c.l.c). We never heard
>of a PID either. F'ups set.
Really? You must be a hobbyist programmer.
>
I have never heard of "F'ups".
for decades now...
Comment