From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1435c2b7fb3842951b2fbc204e2fd3f8@swtch.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] bringing down vacfs in p9p From: "Russ Cox" Date: Thu, 9 Mar 2006 09:01:38 -0500 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 1037c596-ead1-11e9-9d60-3106f5b1d025 > In plan 9 I can do an rm /srv/vacfs.test which immediately > removes the file causing vacfs to exit. This is only true if vacfs is not mounted anywhere. If someone's using it, removing the srv file won't make vacfs exit. Vacfs exits when reading from its 9P pipe returns eof. That happens on Plan 9 when all references to the other end of the pipe have gone away. > It'd be nice if rm `{namespace}^/vacfs.test would do the > same in p9p but it doesn't since unix won't remove the socket file > until vacfs closes it. I've resorted to 9 kill vacfs | rc > which doesn't seem right. > > Is there something I'm missing? Is kill not that bad? Kill is not that bad. If you wanted to simulate Plan 9 and force an eof on the 9P pipe, you could kill the appropriate 9pserve. I can't think of any file servers that need to be shut down gracefully on p9p except acme (which has an Exit command). Russ