05-16-2011
Thanks for you reply.
I got this solved. The solution seems very silly and I should had checked long ago.
Solution: I updated the version of X11 app on the client MAC to the latest and it stopped creating those .Xauthority-c files.
---
If it helps, with the older version of the X11 apps, I was able to get it done by unchecking the “Enable Authentication” from the preferences of X11 app.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: Kevin Pryke
2 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: Bab00shka
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
I would like to lock a file using korn Shell Script before coping the contents of the file.
Do let me know
Thanks in Advance.
Senone (3 Replies)
Discussion started by: senone
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
Does anyone know what happens when two processes are simultaneously trying to write to a single file in UNIX (AIX)?
Cheers (1 Reply)
Discussion started by: penfold
1 Replies
5. UNIX for Dummies Questions & Answers
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)
Discussion started by: thanuman
1 Replies
6. AIX
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)
Discussion started by: crothecker
3 Replies
7. UNIX Benchmarks
Someone know something about this error ?
We have 5.2 and HACMP Cluster. (1 Reply)
Discussion started by: hjara
1 Replies
8. UNIX for Dummies Questions & Answers
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)
Discussion started by: yang
3 Replies
9. UNIX for Dummies Questions & Answers
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)
Discussion started by: yang
2 Replies
10. UNIX for Advanced & Expert Users
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 OPENDARWIN
rpc.lockd
RPC.LOCKD(8) BSD System Manager's Manual RPC.LOCKD(8)
NAME
rpc.lockd -- NFS file locking daemon
SYNOPSIS
rpc.lockd [-d debug_level] [-g grace period]
DESCRIPTION
The rpc.lockd utility provides monitored and unmonitored file and record locking services in an NFS environment. To monitor the status of
hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8).
Options and operands available for rpc.lockd:
-d The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are
logged with level LOG_DEBUG and facility LOG_DAEMON. Specifying a debug_level of 1 results in the generation of one log line per
protocol operation. Higher debug levels can be specified, causing display of operation arguments and internal operations of the dae-
mon.
-g The -g option allow to specify the grace period, in seconds. During the grace period rpc.lockd only accepts requests from hosts
which are reinitialising locks which existed before the server restart. Default is 30 seconds.
-w The -w option tells rpc.lockd to wait until the first client locking request is made before starting the locking daemon(s). This may
be used on NFS clients to defer starting the NFS locking daemons until it is known that they will be needed. (Note: rpc.statd(8)
will also be started if it isn't already running)
Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON.
The rpc.lockd utility must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead,
it should be configured in rc.conf(5) to run at system startup.
FILES
/usr/include/rpcsvc/nlm_prot.x RPC protocol specification for the network lock manager protocol.
SEE ALSO
syslog(3), rc.conf(5), rpc.statd(8)
BUGS
The current implementation serialises locks requests that could be shared.
STANDARDS
The implementation is based on the specification in "Protocols for X/Open PC Interworking: XNFS, Issue 4", X/Open CAE Specification C218,
ISBN 1 872630 66 9.
HISTORY
A version of rpc.lockd appeared in SunOS 4.
BSD
September 24, 1995 BSD