On Fri, 25 Nov 1994, Andrew Valencia wrote:
> [Ronald Oussoren <roussor@cs.vu.nl> writes:]
>
> >Is there a way to cleanly stop a file server (that is stop the file server,
> >and remove its name from the namer)?
>
> Namer currently does not track server deaths. All VSTa servers to this
> point are written so you can just kill them; I'd like to keep this semantic
> as UNIX's shutdown/fsck/lost+found tedium has caused a lot of grief over the
> years.
>
> I've looked at making namer track registered server deaths; so far I haven't
> been able to convince myself that a kernel mechanism is called for. As it
> stands now you try to mount the server name and you get a failure. With
> server death tracking you still get a failure. The only difference is that
> an "ls" of the namer will show the entry. Is it worth more ring 0 code just
> to cover a relatively minor exception condition?
>
Seems that namer will need to handle deaths at least of servers which are
across the network. Maybe this is indeed useful for local servers also
to maintain consistency. It is also frustrating to find a failure which
is not obvious. Since a remote user could kill a server (with
appropriate permission) a local user would not know why an access is
failing.
If I am lost out in the weeds, let me know :)
dave
Received on Mon Nov 28 06:20:35 1994
This archive was generated by hypermail 2.1.8 : Thu Sep 22 2005 - 15:12:10 PDT