Hi,
Sorry for not replying immediately. I could not reboot the NFS server
till to-day
since users were running long jobs.To-day(13th.Mar.2003) I did it.
Now vi is working again. Thanks to the following persons who gave
valuable
suggestions:
Dave Love wrote:
============
I expect it's trying to do file locking and the server doesn't support
that (through lockd?). It will time out after a while. You can check
by running trace or truss on the process if you have one of them
installed.
Browett Darren suggested:
===================
I had the same problem, my NFS server was configured as a disk service
running
on 4.0f. It should have been configured as a "NFS Service" By running it
as a disk
service, two processes where NOT started, and they are :
root 5284 1 0.0 Mar 02 ?? 18:24.15
/usr/sbin/rpc.lockd -b socrates
root 5286 1 0.0 Mar 02 ?? 0:00.01
/usr/sbin/rpc.statd -b socrates
where socrates is the name of the service.
In all there should be 4 processes running on the server, and two on the
clients.
root 5284 1 0.0 Mar 02 ?? 18:24.15
/usr/sbin/rpc.lockd -b socrates
root 5286 1 0.0 Mar 02 ?? 0:00.01
/usr/sbin/rpc.statd -b socrates
root 1247 1 0.0 Mar 02 ?? 0:00.01
/usr/sbin/rpc.statd
root 1249 1 0.0 Mar 02 ?? 0:00.01
/usr/sbin/rpc.lockd
Once I started the rpc -b <service> processes, my locking problems went
away.
The issue lies with the 5.x O/S where they have introduced locking into the
kernel ( or something along those lines)
Elizabeth Harvey-Forsythe wrote:
================================
My guess is that this is a locking problem. vi will lock files, unlike emacs
or some other editors. See if reconfiguring the automount to not use
locking makes a difference.
Willis, Daniel L. gave the following suggestion:
===============================================
This sounds a lot like an NFS locking problem. If you're still having
problems look into the daemon log from the host that serves the home file
system. I expect you will see something about "can not lock" on some file,
or some message related to flock. I expect the rpc services on the system
listed in the daemon file (NFS client) are messed up. The only way I have
been able to get around this in the past was to reboot the NFS client
holding the lock.
My Question was:
================
> Hallo,
> I have installed 5.1a on 3 of our machines. We use NIS
> and automount to mount the user home directories. I
> Have noticed a peculiar problem with vi editor on these
> machines. I can create new files in home directory with
> vi editor without problems. But I cannot reedit these
> files with vi editor. When I start vi on an
> existing file the system waits waits an waits without
> opening it. I can write <ctrl> C and then
> I get a blank editor window. When I write :r filename in
> vi command mode,the system waits again without
> opening the file. I can do any vi operation on machine
> local file systems. I cannot do it on NIS+NFS mounted
> FS systems.(home directory). I can execute the command on
> NFS(without automount+NIS) FS.
> I can work with other editors like edt, nedit etc.
>without any problems.
> Thanks in advance,
> Kumar
Received on Wed Mar 13 2002 - 07:26:02 NZDT