Hi,
I'm having problems with a couple of applications and reading about the
problem indicates its probably caused by locking not working correctly
on NFS. The problem seems to lie with the server end of the set up - my
guess is that it's not accepting the locks from the client machine. Both
On Sat, Dec 23, 2006 at 04:53:28PM +0100, Michelle Konzack wrote:
Am 2006-12-14 12:42:13, schrieb [EMAIL PROTECTED]:
On Thu, Dec 14, 2006 at 12:18:27PM -0500, [EMAIL PROTECTED] wrote:
How do I get NFS locking to work? (And why doesn't it just work
anyway?)
I am unable to use
On Wed, 2007-01-03 at 11:40 -0500, [EMAIL PROTECTED] wrote:
On Sat, Dec 23, 2006 at 04:53:28PM +0100, Michelle Konzack wrote:
Am 2006-12-14 12:42:13, schrieb [EMAIL PROTECTED]:
On Thu, Dec 14, 2006 at 12:18:27PM -0500, [EMAIL PROTECTED]
wrote:
How do I get NFS locking to work? (And why
Am 2006-12-14 12:42:13, schrieb [EMAIL PROTECTED]:
On Thu, Dec 14, 2006 at 12:18:27PM -0500, [EMAIL PROTECTED] wrote:
How do I get NFS locking to work? (And why doesn't it just work
anyway?)
I am unable to use monotone properly over an NFS mount because it very
sensibly tries
On Sat, Dec 23, 2006 at 04:53:28PM +0100, Michelle Konzack wrote:
Am 2006-12-14 12:42:13, schrieb [EMAIL PROTECTED]:
On Thu, Dec 14, 2006 at 12:18:27PM -0500, [EMAIL PROTECTED] wrote:
How do I get NFS locking to work? (And why doesn't it just work
anyway?)
I am unable to use
How do I get NFS locking to work? (And why doesn't it just work
anyway?)
I am unable to use monotone properly over an NFS mount because it very
sensibly tries to lock its repository before modifying it.
My only clue to the problem is messages that keep being reported by
logcheck:
Security
On Thu, Dec 14, 2006 at 12:18:27PM -0500, [EMAIL PROTECTED] wrote:
How do I get NFS locking to work? (And why doesn't it just work
anyway?)
I am unable to use monotone properly over an NFS mount because it very
sensibly tries to lock its repository before modifying it.
My only clue
Hi!
Is there a special nfs locking daemon for NFS-clients?
I'm running a server with nfs-kernel-server and on the server there is a
lockd process. If I try to log into GNOME 2.2 on the client (which has
nfs-mounted home directories), GNOME complains about a problem with your
operating system
Yes, lockd. You need to run it on the clients.
Awais
On Fri, 2004-07-23 at 15:22, Christian Schwarz wrote:
Hi!
Is there a special nfs locking daemon for NFS-clients?
I'm running a server with nfs-kernel-server and on the server there is a
lockd process. If I try to log into GNOME 2.2
In article [EMAIL PROTECTED],
Christian Schwarz [EMAIL PROTECTED] wrote:
Is there a special nfs locking daemon for NFS-clients?
I'm running a server with nfs-kernel-server and on the server there is a
lockd process. If I try to log into GNOME 2.2 on the client (which has
nfs-mounted home
Hi!
After upgrading a diskless client (root fs mounted via NFS) to the GNOME
2.2 backport packages, I get the following error message when logging in
into X:
Could not lock the file /nethome/wile/.gconf-test-locking-file; this
indicates that there may be a problem with your operating system
it was just a couple weeks ago I was trying to help others
on NFS and here I a asking something! doh!
anyways, I noticed recently that my NFS server at home seems to
have trouble with locking. I have 2 clients which use it to host
home directories(1 debian woody, 1 suse 8). I first noticed it
nate wrote:
it was just a couple weeks ago I was trying to help others
on NFS and here I a asking something! doh!
anyways, I noticed recently that my NFS server at home seems to
have trouble with locking. I have 2 clients which use it to host
home directories(1 debian woody, 1 suse 8). I
* On Wed, Sep 04, 2002 at 03:37:07PM -0500, Kent West ([EMAIL PROTECTED]) wrote:
nate wrote:
it was just a couple weeks ago I was trying to help others
on NFS and here I a asking something! doh!
anyways, I noticed recently that my NFS server at home seems to
have trouble with
Hugo Graumann said:
I have had problems with NFS file locking as well. Some parts
of gnome like to use file locking, so with nfs mounted home
directories the users could not really run gnome properly.
that would explain some other problems I had.. I was testing
my mom's GNOME profile and it
Hugo Graumann [EMAIL PROTECTED] [2002-09-04 17:15:14 -0600]:
2) There is a system call to lock a file or parts of a file. In the
Stevens book Advanced Programming for the Unix Environment there
is a whole section on file locking including a c program to lock files.
If locking is
Hi there,
I've been trying to get NFS locking to work on a small network of two
computers, but completely failed on it. Does anybody have experiences on that?
I have tried all kinds of things and read a lot of documentation but found no
hint about what detail I might be missing.
I'm running
On Tue, Jul 10, 2001 at 09:15:56AM +0200, Norbert Nemec wrote:
I've been trying to get NFS locking to work on a small network of two
computers, but completely failed on it. Does anybody have experiences on
that?
I have tried all kinds of things and read a lot of documentation but found
Dietz Proepper [EMAIL PROTECTED] wrote:
that's my first mail to that list - so plz be patient with me ;). Sould
the following be already known - sorry too.
The bug tracking system is your friend :)
http://bugs.debian.org/96864
http://bugs.debian.org/97252
--
Colin Watson
Hi!
I'm trying to set up NFS between two potato boxes running a custom
2.4.1 kernel (Can't change easily neither potato nor this kernel). In
one of the exported directories I need file locking, but get lots of:
Feb 18 14:01:17 kernel: lockd: cannot monitor 192.168.1.1
Feb 18 14:01:17 kernel:
On Sun, Feb 18, 2001 at 06:25:55PM -0300, Christoph Simon wrote:
Hi!
I'm trying to set up NFS between two potato boxes running a custom
2.4.1 kernel (Can't change easily neither potato nor this kernel). In
one of the exported directories I need file locking, but get lots of:
Feb 18
On Sun, 18 Feb 2001 15:11:32 -0900
Ethan Benson [EMAIL PROTECTED] wrote:
On Sun, Feb 18, 2001 at 06:25:55PM -0300, Christoph Simon wrote:
Hi!
I'm trying to set up NFS between two potato boxes running a custom
2.4.1 kernel (Can't change easily neither potato nor this kernel). In
one of
On Sun, Feb 18, 2001 at 09:25:46PM -0300, Christoph Simon wrote:
statd: 192.168.1.1
and such to the proper machines.
Thanks for the reply, but I'm not sure if I understood this. If I put
this line to hosts.deny, wouldn't this mean to explicitly deny access
of this computer? But if
On Sun, 18 Feb 2001 15:31:59 -0900
Ethan Benson [EMAIL PROTECTED] wrote:
you need it in hosts.allow. ALL: PARANOID might be causing the
problem here since NAT lans rarely have reverse DNS working properly.
There is no NAT here (yet), but I do have a properly working local
DNS. Now I have
[EMAIL PROTECTED] wrote:
I have a Debian box running as a Samba server, with mostly NFS mounted drives.
When the users try to access files that need locking,, like Access
databases, it can't lock the file, and won't allow them to open it.
How *does* one get Linux to do real NFS locking
) that to the lockfile - that's guaranteed atomic,
even over NFS.
On the same note, supposing that NFS locking works fine in FreeBSD, would
that be erased if exporting to a linux box? (Exporting from linux
wouldn't work since the NFS locking in linux doesn't work; but would
exporting *to* linux work
26 matches
Mail list logo
