By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,935 Members | 1,559 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,935 IT Pros & Developers. It's quick & easy.

Thread-safe file locking

P: n/a
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?

- Matt

Sep 15 '07 #1
Share this Question
Share on Google+
15 Replies


P: n/a
Matt Brandt wrote:
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?
comp.programming.threads or an OS programming group would be a more
appropriate place to ask this. Neither C nor C++ have standard thread
or file locking support.

--
Ian Collins.
Sep 15 '07 #2

P: n/a

Hi,

Maybe use a piece of code in your program to keep track of which thread
locked which region. Protrecting that piece of code with a mutex. Most
system support mutexes ( for instance sunos, MS-Windows and I believe linux)
..
Regards, Ron AF Greve

http://www.InformationSuperHighway.eu

"Ian Collins" <ia******@hotmail.comwrote in message
news:5l************@mid.individual.net...
Matt Brandt wrote:
>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?
comp.programming.threads or an OS programming group would be a more
appropriate place to ask this. Neither C nor C++ have standard thread
or file locking support.

--
Ian Collins.

Sep 15 '07 #3

P: n/a
Matt Brandt wrote:
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 Standard C and C++ assume that there is nothing else running besides
your program, and both languages don't support threads. Therefore, there is
no concept of "file locking". To do what you want, you have to resort to
system-specific libraries.

Sep 15 '07 #4

P: n/a
Matt Brandt wrote:
>
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.

--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>

--
Posted via a free Usenet account from http://www.teranews.com

Sep 15 '07 #5

P: n/a
ks
On Sep 14, 9:38 pm, CBFalconer <cbfalco...@yahoo.comwrote:
Matt Brandt wrote:
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.
Is your advertisement off topic?

Sep 15 '07 #6

P: n/a
Ron AF Greve wrote:

Please stop top posting. Your reply wasn't even a follow up to mine.

--
Ian Collins.
Sep 15 '07 #7

P: n/a
OK, well which ones then?

On 15 Sep 2007 at 12:06, Rolf Magnus wrote:
Matt Brandt wrote:
>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 Standard C and C++ assume that there is nothing else running besides
your program, and both languages don't support threads. Therefore, there is
no concept of "file locking". To do what you want, you have to resort to
system-specific libraries.
Sep 15 '07 #8

P: n/a
In article <sl********************@nospam.invalid>,
Matt Brandt <ma***@mailinator.comtop-posted
>On 15 Sep 2007 at 12:06, Rolf Magnus wrote:
>Matt Brandt wrote:
>>I am trying to get multiple threads to lock specific regions of a file.
>To do what you want, you have to resort to
system-specific libraries.
>OK, well which ones then?
Putting on my mind-reading hat....

....
...
...
...
Got it!

On your system, you need nerf_lock(), quizzle84(),
and (especially), StopTopPosting()
--
"law -- it's a commodity"
-- Andrew Ryan (The Globe and Mail, 2005/11/26)
Sep 15 '07 #9

P: n/a

"Matt Brandt" <ma***@mailinator.comwrote in message
news:sl********************@nospam.invalid...
OK, well which ones then?
Boost has a thread library. Qt has one as well. Hard to say without
knowing what you use.
Sep 15 '07 #10

P: n/a
Duane Hebert wrote:
"Matt Brandt" <ma***@mailinator.comwrote in message
news:sl********************@nospam.invalid...
>OK, well which ones then?

Boost has a thread library. Qt has one as well. Hard to say without
knowing what you use.
Or even which language...

--
Ian Collins.
Sep 15 '07 #11

P: n/a

"Ian Collins" <ia******@hotmail.comwrote in message
news:5l*************@mid.individual.net...
Duane Hebert wrote:
>"Matt Brandt" <ma***@mailinator.comwrote in message
news:sl********************@nospam.invalid...
>>OK, well which ones then?

Boost has a thread library. Qt has one as well. Hard to say without
knowing what you use.
Or even which language...
Missed the cross post. If the OP is using C only,
pretty much lets out my suggestions...
Sep 15 '07 #12

P: n/a
Matt Brandt wrote:
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?
You should not be using file locking to protect between the same
threads. On the other hand, if the file handles are different, it may
be that file locking will work even within the same thread on different
file handles.
Sep 16 '07 #13

P: n/a
In article <46***********************@per-qv1-newsreader-01.iinet.net.au>,
Gianni Mariani <gi*******@mariani.wswrote:
>Matt Brandt wrote:
>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?
>You should not be using file locking to protect between the same
threads. On the other hand, if the file handles are different, it may
be that file locking will work even within the same thread on different
file handles.
Unfortunately your answer to this off-topic question was not correct.
POSIX, for example, defines most attributes as being related to
the file descriptor (fd), not the file handle (FILE*) --
but when it comes to POSIX locking:

NOTES
Locks are on files, not file descriptors. That is, file descriptors
duplicated through dup(3C) (but not through fork(2), see the BUGS section
below) do not result in multiple instances of a lock, but rather multiple
references to a single lock.

This has some interesting and probably unintended consequences that can
result in early loss of the lock.

Correct locking is platform specific, and needs to be referred to
a platform specific newsgroup.
--
"It is important to remember that when it comes to law, computers
never make copies, only human beings make copies. Computers are given
commands, not permission. Only people can be given permission."
-- Brad Templeton
Sep 16 '07 #14

P: n/a
CBFalconer <cb********@yahoo.comwrites:
Matt Brandt wrote:
>>
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".

"We" speak English is this news group. Kindly be courteous and consider
people whose first language is not English and would have problems
decoding your awful tendency to "jive" in your replies.
>
--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>
Sep 16 '07 #15

P: n/a
Richard <rg****@gmail.comwrote in news:7v************@individual.net:
CBFalconer <cb********@yahoo.comwrites:
>Matt Brandt wrote:
>>>
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".
F'ups: Follow-ups. That particular contraction has been used on USENET
for decades now...
Sep 17 '07 #16

This discussion thread is closed

Replies have been disabled for this discussion.