🚀 go-pugleaf

Scott A. McIntyre writes
> Whilst mucking around with installing DNS stuff, I have somehow managed to  
lose the
> ability to render on my NSC machine.  I was able to do it when I first  
installed 3.0, but
> i've had to customise it so much that I can't remember what was changed and  
where.
> 
> When I try to render anything to localhost, I get a popup window that  
complains that it
> "Couldn't connect to localhost" and then dies.
> 
> Can someone with 3.0 and working rendering, please tell me what I should have  
aliased in
> /etc/hosts, or in netinfo, or wherever, or what should be running, and so on!
> 
> Thank you!
> Scott
> 
Here is a configuration that works for me, in my two-level [network and local]  
netinfo setup, which makes no reference to "localhost".  Perhaps it will help  
you out.

At both the network level and the local leves one finds a directory named  
/locations/renderers.  This directory has the property value pairs:
  name      renderers
  _writers  *

Under the network /locations/renderers directory, there is a subdirectory named  
lilliput (the name of this machine).  The property/value pairs attached to this  
/locations/renderers/lilliput directory are:
  name      lilliput
  _writers  *
  note      Lilliputian render engine

This seems to do the trick; the render panel pops up with the one possible  
entry and when one clicks on it, the renderer happily proceeds:

lilliput> ps -ax | grep render
  216 ?  S     0:02 rpc.renderd
  769 ?  R     0:01 prman tiffrender.000.rib
  771 p1 S     0:00 grep render
lilliput> 

Do you have an rpc.renderd going on your machine?

There is this question of why, when there is one entry on the list of  
possibilities, one cannot short-circuit the panel entirely, but that's  
something to be asked of c.s.n.programmer I guess.

Good luck.

-- joseph