02-25-2009
How are you creating the race condition?
You can easily prevent race conditions by creating a temporary file and using rename() to replace the file after checking the timestamp of the original file.
If only your program is changing the file, you can also use flock(fd, LOCK_EX) so that if another instance of your program also uses flock() it will block until the other instance finishes processing or calls flock(fd, LOCK_UN).
Keep in mind that flock() doesn't prevent file unlink()ing.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'm currently writing a bash script, that starts multiple threads:
____________________
#!/bin/bash
loop=0
while((loop!=10))
do
thread &
((loop++))
done
#wait for all sub-processes (thread) to finish
wait
___________________
Now I want to know, what happens, if a... (2 Replies)
Discussion started by: tho99
2 Replies
2. Linux
In unix how we can test or check race condition in any c program by using multi thread programming (1 Reply)
Discussion started by: afroze
1 Replies
3. UNIX for Dummies Questions & Answers
In unix how we can test or check race condition in any c program by using multi thread programming (1 Reply)
Discussion started by: afroze
1 Replies
4. Programming
In unix how we can test or check race condition in any c program by using multi thread programming (1 Reply)
Discussion started by: afroze
1 Replies
5. Programming
I've been experimenting with pseudo-terminals and found something I don't quite understand. Writing an EOF character to the master end doesn't work quite as I expect. Once I've written any other data, the master pty seems to treat a single ^D as a seperator, i.e. writing "abcabc" would let cat do... (1 Reply)
Discussion started by: Corona688
1 Replies
6. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
7. Programming
Hi all,
i'm reading Andrew S.Tanenbaum's book --- Modern Operating System.At the part of discussing race condition.And the author gives a solution with using the TSL instruction,say that one process must call the enter_region function before entering the critical regions and call the leave_region... (0 Replies)
Discussion started by: homeboy
0 Replies
8. Shell Programming and Scripting
I want to make a script that check for the argument passed to it and generates an error in case any character/string argument passed to it.
I am using below code, but its not working. can anyone help.
#!/bin/bash
if ]; then
echo 'An integer argument is passed to the script hence... (3 Replies)
Discussion started by: mukulverma2408
3 Replies
9. Shell Programming and Scripting
I want to know the if condition in checking the hostname in unix and then running a cron job (all in a single line)
Thanks (2 Replies)
Discussion started by: prash358
2 Replies
FLOCK(2) BSD System Calls Manual FLOCK(2)
NAME
flock -- apply or remove an advisory lock on an open file
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <fcntl.h>
#define LOCK_SH 1 /* shared lock */
#define LOCK_EX 2 /* exclusive lock */
#define LOCK_NB 4 /* don't block when locking */
#define LOCK_UN 8 /* unlock */
int
flock(int fd, int operation);
DESCRIPTION
flock() applies or removes an advisory lock on the file associated with the file descriptor fd. A lock is applied by specifying an operation
parameter that is one of LOCK_SH or LOCK_EX with the optional addition of LOCK_NB. To unlock an existing lock operation should be LOCK_UN.
Advisory locks allow cooperating processes to perform consistent operations on files, but do not guarantee consistency (i.e., processes may
still access files without using advisory locks possibly resulting in inconsistencies).
The locking mechanism allows two types of locks: shared locks and exclusive locks. At any time multiple shared locks may be applied to a
file, but at no time are multiple exclusive, or both shared and exclusive, locks allowed simultaneously on a file.
A shared lock may be upgraded to an exclusive lock, and vice versa, simply by specifying the appropriate lock type; this results in the pre-
vious lock being released and the new lock applied (possibly after other processes have gained and released the lock).
Requesting a lock on an object that is already locked normally causes the caller to be blocked until the lock may be acquired. If LOCK_NB is
included in operation, then this will not happen; instead the call will fail and the error EAGAIN will be returned.
NOTES
Locks are on files, not file descriptors. That is, file descriptors duplicated through dup(2) or fork(2) do not result in multiple instances
of a lock, but rather multiple references to a single lock. If a process holding a lock on a file forks and the child explicitly unlocks the
file, the parent will lose its lock.
Processes blocked awaiting a lock may be awakened by signals.
RETURN VALUES
Zero is returned if the operation was successful; on an error a -1 is returned and an error code is left in the global location errno.
ERRORS
The flock() call fails if:
[EAGAIN] The file is locked and the LOCK_NB option was specified.
[EBADF] The argument fd is an invalid descriptor.
[EINVAL] The argument operation does not include exactly one of LOCK_EX, LOCK_SH, or LOCK_UN.
[EOPNOTSUPP] The argument fd refers to an object other than a file.
SEE ALSO
close(2), dup(2), execve(2), fork(2), open(2), flockfile(3), lockf(3)
HISTORY
The flock() function call appeared in 4.2BSD.
BSD
October 15, 2011 BSD