From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Eoghan Sherry <ejsherry@gmail.com>
References: <a2d238df0603090208w29f13e76r@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <a2d238df0603090208w29f13e76r@mail.gmail.com>
Subject: [9fans] bringing down vacfs in p9p
Message-Id: <20060309125755.2A4D210C69@dexter-peak.quanstro.net>
Date: Thu,  9 Mar 2006 06:57:55 -0600
Cc:
Topicbox-Message-UUID: 1031d528-ead1-11e9-9d60-3106f5b1d025

the unix domain sockets in `{namespace} don't need to be removed;
9pserve -- not vacfs -- creats the socket file. it is not removed,
regardless of how things exit.

since vacfs doesn't do rfork(RFNOTEG), hitting delete in the 9term
window from which vacfs was started should kill vacfs off.

i don't see how that could be dangerous since vacfs is only a cache.

- erik

"Eoghan Sherry" <ejsherry@gmail.com> writes

|
| I can't figure out how to gracefully stop vacfs (or any other
| file server for that matter) in p9p.
|
| In plan 9 I can do an rm /srv/vacfs.test which immediately
| removes the file causing vacfs to exit.
|
| 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?
|
| eoghan