From owner-freebsd-questions Tue Jan 17 16:14:38 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA00249 for questions-outgoing; Tue, 17 Jan 1995 16:14:38 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id QAA00242 for ; Tue, 17 Jan 1995 16:14:37 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA25382; Tue, 17 Jan 1995 19:11:53 -0500 Date: Tue, 17 Jan 1995 19:11:53 -0500 From: Garrett Wollman Message-Id: <9501180011.AA25382@halloran-eldar.lcs.mit.edu> To: "M.C Wong" Cc: freebsd-questions@freefall.cdrom.com (freebsd-questions@freefall.cdrom.com) Subject: what are these .nfs* files ? In-Reply-To: <199501172326.AA259605163@hp.com> References: <199501172326.AA259605163@hp.com> Sender: questions-owner@FreeBSD.org Precedence: bulk < said: > Hi, > I wonder what are those $HOME/.nfs* files for ? I mean how do > they relate to nfs mounted filesys ? You get these when one process deletes a file while another process (on the same machine) is still accessing it. From nfs_vnops.c: /* * nfs file remove call * To try and make nfs semantics closer to ufs semantics, a file that has * other processes using the vnode is renamed instead of removed and then * removed later on the last close. * - If v_usecount > 1 * If a rename is not already in the works * call nfs_sillyrename() to set it up * else * do the remove rpc */ -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant