08-16-2010
mandatory & record locking using client server architecture
Hi
I want a program of employee database locking with mendatory & record locking using client server architecture .there are two type of clients one which has all permissions of read/write called supervisor & another can only read the file.employee data base should contain
1) name
2)ID
3)BU
4)Sal
5)time stamp(last modified)
Last edited by rluha; 08-16-2010 at 03:29 PM..
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I've been running Django on MySQL on a Linux server for about 3 months w/o any problem. Suddenly a couple days ago, the server Django began throwing errors about not being able to connect to MySQL, at which point the entire server seizes up. The Apache Web server stops serving pages and SSH seizes... (3 Replies)
Discussion started by: mongoose1
3 Replies
2. Programming
What is the difference between mutex_lock and pthread_mutex_lock ? Should I use both when using binary semaphores.
Also, what is the difference between using a binary semaphore and a counting semaphore where you wait on the condition variable ? (1 Reply)
Discussion started by: joey
1 Replies
3. UNIX for Dummies Questions & Answers
Hi everyone! I'm totally new to Unix/Linux. In my last job I was able to be exposed a little bit by using unbuntu desktop for 11 months and also the xemacs editor. I basically know nothing and I'm totally interested in ditching the Microsoft Environment.
I would like to build a file server... (1 Reply)
Discussion started by: jtaylor69
1 Replies
4. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
5. Shell Programming and Scripting
Hi all,
Can anyone help ...on how to ensure that a file is locked .
thanks & regards,
Soodoo
----------------------------------------
Problem description: -
We usually use the mv command in scripts to make sure that a file is complete and not being written to by another process.
... (1 Reply)
Discussion started by: soodoo
1 Replies
6. Windows & DOS: Issues & Discussions
Hi All,
I need your expertise in finding a way to solve my problem.Please excuse if this is not the right forum to ask this question and guide me to the correct forum,if possible.
I am a DBA and on a daily basis i have to ftp huge dump files from my company server to my laptop and then... (3 Replies)
Discussion started by: kunwar
3 Replies
7. IP Networking
First of all, hello.
I have a problem installing a vpn server and client.
My server is a computer running windows 7, and windows, running a virtual machine running debian.
In the debian system, I've the vpn server installed (SoftEther VPN Server)
The problems come when I try to connect to... (1 Reply)
Discussion started by: Blues23
1 Replies
8. UNIX and Linux Applications
Good afternoon
I need your help please.
There is a Mantenance Windos which needs to Restart de Database Server 192.x.x.97 to set up some configuration
Is it mandatory or not to stop/start Applcation server that runs in 192.x.x.95 ?
Is it mandatory or not to stop/start apache and Tomcat?... (3 Replies)
Discussion started by: alexcol
3 Replies
lockd(8c) lockd(8c)
Name
lockd - network lock daemon
Syntax
/usr/etc/lockd [ -t timeout ] [ -g graceperiod ]
Description
The daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking service
makes this advisory locking support possible by using the system call and the subroutine. The daemon forwards lock requests for remote
data to the server site's lock daemon. The daemon then requests the status monitor daemon, for monitor service. The reply to the lock
request is not sent to the kernel until the status daemon and the server site's lock daemon have replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site daemons to submit reclaim requests. Client site daemons are noti-
fied by of the server recovery and promptly resubmit previously granted lock requests. If a client site's daemon fails to secure previ-
ously granted locks at the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
cannot reclaim them.
Options
-t timeout The daemon uses timeout (in seconds) as the interval instead of the default value of 15 seconds to retransmit a lock
request to the remote server.
-g graceperiod The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.
See Also
fcntl(2), lockf(3), signal(3), statd(8c)
lockd(8c)