Hi all,
One of our administrators is having a problem with pico over NFS. The
details are below. Anyone seen anything like this? How did you fix it?
Thanks.
Teresa
-------- Original Message --------
Subject: Problem with digital unix, NFS and pico/pine
Resent-Date: Thu, 30 Jan 2003 14:02:59 -0500 (EST)
Resent-To: tpbsys_at_osfmail.isc.rit.edu
Date: Thu, 30 Jan 2003 14:01:41 -0500 (EST)
From: Jim Bodie <jabpci_at_cis.rit.edu>
To: tpbsys_at_vmsmail.rit.edu
Teresa,
Report of the NFS/pico/pine file issue
The issue: Any file edited with pico, with data removed, will appear to
replace
the file with null characters. The problem is not only with pico, but
pico is
a easy way to recreate the problem.
The specifics:
The file server is a DS-20E running DU 5.1A with patch kit 3.
The clients don't matter. This has worked for Solaris 7, Solaris 8 and
DU 4.0f
clients. We have no DU 5.1A clients as we are not upgrading any more
alphas
until a fix is found.
The version of pico does not matter, we have 3 different versions on our
servers
and the results are the same. Specifically pico versions 4.4 (4.53),
3.7
(4.21), and 3.9 (4.31). The number is parentheses is the version of
pine that
pico comes with.
How to make the problem happen:
The only time pico does not wipe out the file is when it is executed
locally on
the file server.
The steps in making the problem:
- Start with a text file.
- edit the file with pico.
- remove any text, 1 or more characters
- write the file and exit
- The file on the NFS client will be the same number of characters, but
they
will all be NULL. On the NFS server, the file will be fine. If you
vi the
file (on the server) and do an immediate write-quit (:wq), the file
will then
be fine on the server and client.
If you are logged onto the server and do the above test, pico will not
clobber
the file. If you add text to the file, the problem does not seem to
occur.
Thanks,
Jim Bodie
475-6160
// Jim Bodie, RIT Center for Imaging Science, <jabpci_at_cis.rit.edu>
Received on Thu Jan 30 2003 - 19:11:46 NZDT