[OpenAFS-devel] on sockets and devices in AFS

[Derrick Brashear]

On Sep 16, 2010, at 11:14 AM, Tom Keiser <tkeiser@sinenomine.net> wrote:

> On Thu, Sep 16, 2010 at 9:58 AM, Derrick Brashear <shadow@dementia.org> wr=
ote:
>> Long has it been the case that people have wanted the ability to create s=
pecial devices and sockets in AFS, yet due to the non-portability of these w=
e haven't been able to do it.
>>=20
>> Can I suggest we consider
>> 1) allowing these to be created but not sent to the server
>> 2) if created locally they would cover a later file of the same name if o=
ne is created
>> 3) when disconnected AFS persists data across reboots, it be used to pers=
ist this data on the local client.
>> 4) until then, and even then for memcache, a config file which is updated=
 as these are created and removed, and reread at AFS start to recreate state=
.
>>=20
>=20
> This is an interesting concept.  I do have two small concerns:
>=20
> 1) to some degree, the local filename overlay semantics violate the
> principle of least surprise; and

so does 'can't create a socket'

> 2) it should be done in such a manner that any envisioned support for
> distributed sockets/named pipes not be precluded.

indeed. I have no easy answer there=