[Bf-committers] RenderD Info
Mon, 14 Apr 2003 10:01:15 -0400
On Friday, April 11, 2003, at 03:52 PM, Hans Lambermont wrote:
>> Everything runs fine... but when I fire up renderd in the same
>> directory as the blender executable, I get:
>> Thread 1 Crashed:
>> #0 0x00019db0 in PR_EnumerateHostEnt (prnetdb.c:1236)
>> #1 0x00003ac4 in renderd_scan_thread (scan.c:34)
> Hmm. this could be caused by the scanner being quite blunt in searching
> for servers (or clients, was this a server or a client ?)
Server. I launched RenderD and it informed me (via console) "Launching
./blender" followed by a pause then the abovementioned crash.
> Try disabling the scanner and use the telnet interface to connect the
> client to the server (or vice versa ;-)
Haven't gotten to the point where I can launch the client... the server
won't stay up. :-)
> Ehh, there shouldn't be a window. Blender is used in render-only mode.
> Which is most probably broken now. Try 'blender -b' it should end with
> 'Blender quit' immediately, without generating a window.
It does: blender immediately quits since there isn't anything to
render. :-) I wasn't expecting a window, but since typing ./blender
from the command line DOES generate a window then the ./renderd command
executing ./blender should generate one, too. Unless there's a command
line option that I don't know about?
Thanks for the config.guess tip. Should I also use this for blender, or
has that one already been updated?
I am executing renderd from a directory that has a copy of the
/blender.app/Contents/MacOS/blender executable in it directly. When I
compile blender, I get an executable AND a blender.app: I'm using the
Help appreciated! I have ambitions of putting a rendering machine on my
network to pass off anims and test frames to while I"m modeling.