8 More Discussions You Might Find Interesting
1. Programming
Suppose I have 5 independent process divided in two imaginay sets:
set1 set2
---------------------
p1 p3
| |
p2 p4
|
p5
The processes inside each set communicate mutually quite often.
I mean p1 and p2 communicate mutually quite often
Similarly p3, p4 and p5 communicate mutually... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
2. Shell Programming and Scripting
What if the operating systems would not use any ipc mechanism in order to exchange the datas with each other,which technique could be an alternative for messaging between the processes?Do you guys think using the vfork () system call to duplicate processes is a logical solution for this problem? (4 Replies)
Discussion started by: helltrex
4 Replies
3. Shell Programming and Scripting
Hello Folks,
I got an issue to be solved. I need to show the user a progress bar while executing an process using shell script
Example:
While updating firmware lets assume this will take 2 min to upgrade i need the shell script to show the progress bar as (0%) and at the end it should... (13 Replies)
Discussion started by: phanivarma
13 Replies
4. Programming
OIOIC is a completely new object-oriented mechanism for the C programming language.
Please download the "OIOIC-Primer-2nd-Edition-English.tar.gz". (the English version of << OIOIC Primer >> )
http://code.google.com/p/oioic/downloads/list
Welcome your advice!
Using OIOIC, you can describe... (7 Replies)
Discussion started by: pervise.zhao
7 Replies
5. Solaris
hi,
I have some windows client machines which require a signal to be sent by a Solaris machine( SunOS 5.6) when ever a particular event occurs on that Solaris machine. What are possible communication mechanisms by which i can do this.
the constraints are
> the windows machines have to... (7 Replies)
Discussion started by: Krsh
7 Replies
6. AIX
Hi all,
on aix,whether have udev or devfs mechanism?
thanks! (4 Replies)
Discussion started by: anonys
4 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
Like in windows OS we have in unix something called "jobs"-term me if i am wrong- to run a sequence of steps which we can exceute at our own will without scheduling like corntab scheduling. can any one tell me what is the structure of this file and provide me with some info with this... (5 Replies)
Discussion started by: aixjadoo
5 Replies
8. Programming
Hi,
The description and the context of the mechanism that i require is as follows:
There is an application communicating with a protocol stack binary. There is a TCP socket communication between the two.
Now, the stack is pumping up data to the Application such that the receiving buffer of... (2 Replies)
Discussion started by: saptarshi
2 Replies
LEARN ABOUT DEBIAN
dotlock
dotlock(1) Mail Avenger 0.8.3 dotlock(1)
NAME
dotlock - execute a command with a lock on a mailbox
SYNOPSIS
dotlock [-LPW] mbox-file command [arg ...]
DESCRIPTION
dotlock acquires a lock on the mailbox file mbox-file using both flock and a lock file, then executes command with any arguments specified.
When command exits, dotlock releases the lock.
dotlock attempts to clean up stale lockfiles. If it succeeds in locking an mbox-file with flock, and roughly 30 seconds elapse without
there being any changes to mbox-file or the lockfile, then dotlock will delete the lockfile and try again.
While it holds a lock, lockfile will keep updating the modification time of the lockfile every 15 seconds, to prevent the lock from getting
cleaned up in the event that command is slow.
OPTION
--noflock (-L)
Ordinarily, dotlock uses both flock and dotfile locking. (It uses flock first, but releases that lock in the even that dotfile locking
fails, so as to avoid deadlocking with applications that proceed in the reverse order.) The -L option disables flock locking, so that
dotlock only uses dotfile locking.
This is primarily useful as a wrapper around an application that already does flock locking, but to which you want to add dotfile
locking. (Even if your mail delivery system doesn't use flock, flock actually improves the efficiency of dotlock, so there is no
reason to disable it.)
--fcntl (-P)
This option enables fcntl (a.k.a. POSIX) file locking of mail spools, in addition to flock and dotfile locking. The advantage of fcntl
locking is that it may do the right thing over NFS. However, if either the NFS client or server does not properly support fcntl
locking, or if the file system is not mounted with the appropriate options, fcntl locking can fail in one of several ways. It can
allow different processes to lock the same file concurrently--even on the same machine. It can simply hang when trying to acquire a
lock, even if no other process holds a lock on the file. Also, on some OSes it can interact badly with flock locking, because those
OSes actually implement flock in terms of fcntl.
--nowait (-W)
With this option, dotlock simply exits non-zero and does not run command if it cannot immediately acquire the lock.
SEE ALSO
avenger(1), deliver(1), avenger.local(8)
The Mail Avenger home page: <http://www.mailavenger.org/>.
BUGS
dotlock does not perform fcntl/lockf-style locking by default. Thus, if your mail reader exclusively uses fcntl for locking, there will be
race conditions unless you specify the --fcntl option.
flock does not work over network file systems. Thus, because of dotlock's mechanism for cleaning stale lock files, there is a possibility
that a network outage could lead to a race condition where the lockfile is cleared before command finishes executing. If lockfile detects
that the lock has been stolen, it prints a message to standard error, but does not do anything else (like try to kill command).
AUTHOR
David Mazieres
Mail Avenger 0.8.3 2012-04-05 dotlock(1)