On 1/19/07, Keith Waters <[EMAIL PROTECTED]> wrote:
14:20:09 open("management.phtml", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3
Is it having trouble opening the file for writing?
well, "it" is not having any trouble, because the call to open()
succeeds. The drive, the operating system, etc -- any
Sorry, forgot to hit 'send' on this one
strace -f -e trace=file vim some-text-file 2>/dev/pts/23
Thanks, this is a brilliant new tool to have! I added -t for
timestamps this is what happens... (Note the 20 second delay in the
middle of the log)
*** SAVE FILE START
14:20:09 g
It is running on the server and there is no network? How come?
I thought you meant am I running it over a shared drive - the answer is no.
I ssh into the box and run vim (binary) on the same box (and drive) as the
file I am editing.
When you said that saving files takes almost 11 second
On 18Jan2007 09:23, Tim Chase <[EMAIL PROTECTED]> wrote:
| >It's running on the server, no network involved. Just a standard
| >out-of-the box enterprise linux installation (ie installed from rpm)
|
| Other things one might want to investigate:
|
| - does it happen when you start with "vim -u
It's running on the server, no network involved. Just a standard
out-of-the box enterprise linux installation (ie installed from rpm)
Other things one might want to investigate:
- does it happen when you start with "vim -u NONE" (eliminate
possible plugin/script problems)
- is your hard-dr
It's running on the server, no network involved. Just a standard
out-of-the box enterprise linux installation (ie installed from rpm)
Keith
How are you using VIM? The binary is in the server? Or the shared libs
are in the server...I dont know where exactly the problem can be.
Some NFS or SS
How are you using VIM? The binary is in the server? Or the shared libs
are in the server...I dont know where exactly the problem can be.
Some NFS or SSH?
Last year I had the same problems on the lab university, and the
problem was the heavy traffic on the network (bad administration) and
their ba
Hi All.
One of my new servers, running vim, is taking a very long time to save files
of any size. (We're talking about 11 seconds). The server is not busy at
all ( IO and CPU, I checked using vmstat) and there are no hard drive errors
showing in syslog.
I have no idea where to start looki
