Namespace Caching

["Eric S. Crawley" <Crawley%alderaan.scrc.symbolics.com@RELAY.CS.NET>]

    Date: Thu, 2 Feb 89 14:15:01 PST
    From: saus@venera.isi.edu (Mark Sausville)


    Greetings,

    How many times has it happened?  You need a host in your namespace.
    The guy with the nameserver puts it in the namespace.  Your machine,
    since it already asked the nameserver without success, decides that it
    need never ask again.  "Foo is not a known host".  Anybody know what
    to do to insist that your machine ask the nameserver once more? (yes,
    I know that cold-booting will do it: I was hoping for something a bit
    less violent.)

:Reset Network is simple and usually does the trick.  If you want to
always check with the namespace server for everything, you could set
neti:*validate-once-per-boot* to nil.  This is set to T by default.

A less drastic method would be to do
(neti:reset-all-host-availabilities) to make the namespace server
available if it had been inaccessible followed by
(neti:reset-all-namespace-access-paths) to reset any cached paths to the
namespace server.  This should reset things enough that :Show Namespace
Object should be able to find the object.