Alan Shutko wrote:
> Tim writes:
> > I'm using ftp or lftp, and find a file called (eg) .nfs80301.
>
> Some process has an open handle to the file over NFS.
>
> When you have a program with a file open over NFS, but delete the
> file (over nfs) the file is renamed as you see it. When the process
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derrick 'dman' Hudson wrote:
| On Thu, Aug 07, 2003 at 12:09:07AM +0100, Tim wrote:
|
| | rmdir -f and rm -f both fail. If I delete the offending file, a new one
| | takes its place, named (eg) .nfs90301.
| |
| | Any suggestions?
|
| Find out what is c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Proulx wrote:
| Even though you cannot remove the file it is possible to move the file
| around. You can 'mv .nfs* ../' for example to get the files up a
| level. That empties the directory and would allow you to remove a
| directory for example.
On Thu, Aug 07, 2003 at 12:09:07AM +0100, Tim wrote:
| rmdir -f and rm -f both fail. If I delete the offending file, a new one
| takes its place, named (eg) .nfs90301.
|
| Any suggestions?
Find out what is creating the file, and solve the real issue.
I know it is related to NFS and locking or
Tim <[EMAIL PROTECTED]> writes:
> I'm using ftp or lftp, and find a file called (eg) .nfs80301.
Some process has an open handle to the file over NFS.
When you have a program with a file open over NFS, but delete the
file (over nfs) the file is renamed as you see it. When the process
closes, the
5 matches
Mail list logo