The applications that I want to run are on Linux Server [NFS] and the client machines [CIFS] that are having problem in locking the .Xauthority files are Macs which share the same domain as that of client solaris machine. i.e. The home directory of particular user on Solaris & the home directory of that user on Mac have same contents.
When I ssh -X from Solaris to the server, everything works fine, no error messages.
When I ssh -X from MACs to the server, I get the following warning messages.
/usr/X/bin/xauth is the path on the server. If I try to break the lock by sudo /usr/X/bin/xauth -b quit, I get the following error
When I ssh -X from any my MacBookPro to the server,
I have checked sshd_config on both the server and the Mac clients, there is nothing that seems wrong, but if you guys have insights then please share.
---
Deleting .Xauthority files work, but thats not a good solution. I mean, everytime I have to run any X forwarding application I have to delete the .Xauthority file
I have a set of scripts to do software releases to remote machines which uses ftp. I'm having a problem getting 'lost connection' messages.
What I wanted to ask is, does ftp employ some sort of file locking if two ftp processes are trying to copy the same file at the same time? & if so could... (2 Replies)
Hi,
Simple question but I just need to confirm the answer:
If two or more processes attempt to move the same file at exactly the same time, will unix internal file locking allow only one of the processes to access the file?
Many thanks
Helen :) (2 Replies)
We want to lock a file, during a program(pgm1) execution(until the execution of the program is completed), so that other program(pgm2) can't read/edit that file, until execution of earlier program(pgm1) is completed. How can this be achieved thru shell scripting...
we tried chmod +l option, but... (1 Reply)
Folks,
I am having a minor problem on a new AIX install. I have AIX installed in and LPAR on a p550 and everything works fine with the exception of users who log in with ssh.
It seems that when a user has X11 forwarding enabled in their ssh client and they connect to the server, logins hang.... (3 Replies)
how do i implement file locking in unix?
example if i want to update a file, i would like to use file locking. how do i implement it?
i am using shell script
thanks (3 Replies)
how to ensure all files are being locked while updateing some files?
example when i want to update the password and shadow file in unix. how do i implement file locking??
please advice
thanks (2 Replies)
i am working on a device runnin on linux....i have configured the samba server in the device such that my windows PC can access a shared folder in the device. Also in the device i am runnin some programs which access the files in this shared folder. What i want to know is whether there is any way i... (1 Reply)
Discussion started by: abhinx
1 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)