home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!olivea!charnel!rat!zeus!
- From: Alex Raftis
- Newsgroups: comp.sys.next.misc
- Subject: Re: .nfs*** files getting left all over
- Message-ID: <1993Jan12.224109.105787@zeus.calpoly.edu>
- Date: 12 Jan 93 22:41:09 GMT
- References: <7325@ucsbcsl.ucsb.edu>
- Sender: news@zeus.calpoly.edu
- Reply-To: alex@cosmos.acs.calpoly.edu
- Organization: Cal Poly State University, San Luis Obispo
- Lines: 29
-
- Douglas Scott writes
- >I am finding lots of files named .nfs*** (usually *** = numbers) left around
- >on our filesystem. They seem to be created when using <command>-r to delete
- >files that are on remote filesystems, and I am not sure, but it appears that
- >they do not clear up on their own.
- >
- >I found that I needed to cmd-r the files, and then cmd-r the .nfs files as
- >well!
- >
- >This is definitely new to 3.0 -- anyone have an explanation or suggestion for
- >this? I assume it is some nfs weirdness.
- >
-
- That's a UNIXism, and it can be an extremely bad things to remove. I
- found out the hard way before I knew what they were, and my system
- crashed. The .nfs* files are create when some program has an open
- reference to a file. If you try to remove that file, but something is
- still accessing it, a .nfs* file is created so that they other process
- doesn't loose information it needs.
-
- These will be cleaned up by cron on a nightly basis, usually around 2
- am. Since it's done so late at night, the risk of a system crash due to
- removing an important one is minimized.
-
- Alex
- --
- ______________________________________________________
- Internet: alex@data.acs.calpoly.edu (NeXT mail)
- alex@cosmos.acs.calpoly.edu
-