🚀 go-pugleaf

Hi, I have an un-networked NeXT running NeXTSTEP 3.0, and I can't seem
to get the photoreal RenderMan server running.  I discovered this by
trying the beta copy of Perspective.app and trying to do a full
rendering of an image.  Apparently my machine got configured in such a
way that the rpc.renderd daemon never executes at boot time.

This was confirmed when I checked  /private/adm/messages and found this
note:

Oct  1 14:52:38 localhost inetd[284]: renderd/rpc/udp: unknown service

Running `rpcinfo -p' informed me that all the other inetd programs had
been properly executed.  My suspicion is that rpc.renderd is designed
to be executed remotely and control processes running on several
systems, and for some reason my computer thinks it is networked or
something and thus doesn't find the rpc.renderd daemon.

This is also possibly confirmed by this message in the N3DKit.rtf
document in /NextLibrary/Documentation/NextDev/ReleaseNotes which
states (near the end):

> If you change the name of your host by editing /etc/hostconfig by
> hand, the rendering machinery won't be able to find it.  Local
> rendering will not work.  If you change the name of your host using
> HostManager.app, then you have to further edit the netinfo database in
> the . domain so your host has localhost as an alias.

Now I haven't messed with hostconfig, but possibly I screwed up my
netinfo database or something during my rather difficult upgrade
process.  Does anyone have some advice on how to make the rendering
service work properly on my system?

Thanks,

Shane