From: Dylan Penhale <dylanpenhale@(email surpressed)>
Subject: RE: Shake INIT_Processeses problem
   Date: Tue, 22 Aug 2006 01:31:19 -0400
Msg# 1377
View Complete Thread (10 articles) | All Threads
Last Next
To follow up on this issue, we found that it WAS in fact Quicktime that was
failing. Only on certain machines when trying to render shake scenes
containing Quicktime files. When Quicktime was unable to open an error
dialogue box to inform the user of the error we got the error about the
windows manager being displayed in the shake log, presumably because it gets
written to stderr.

Reinstalling Quicktime on the few boxes with this problem has remedied the
problem.

Thanks Greg


-----Original Message-----
From: Greg Ercolano [mailto:erco@(email surpressed)] 
Sent: 04 August 2006 18:12
To: void@(email surpressed)
Subject: Re: Shake INIT_Processeses problem

[posted to rush.general]

Dylan Penhale wrote:
> I have just noticed that this is happening on some boxes that are not
rendering.

	Hmm, not sure I follow.

	This error shouldn't have anything to do with whether the machines
	are rendering anything.

	The error is caused by shake trying to access the window manager,
	and failing because it isn't being invoked by the same user logged
	into the window manager.

	Actually I doubt it's shake's code that's responsible for the error
	(unless the user is rendering to the screen). It's more likely that
shake
	is loading a dynamic library from the OS (like the quicktime lib),
and
	the library's initialization code is trying to manipulate or in some
way
	access the window manager.

> We have just started rolling out a few of the 102.42a6 update to the 
> farm today. Do you think this is related?

	No, I can't see how the Rush install could impact shake.

	You can replicate this problem with ssh entirely outside of rush,
	so the only possible way rush could affect shake is if rush
manipulated
	the shake directory or the OS libraries.. it doesn't.

	Maybe I'm missing something about your question.
	By what means do you think one program could affect the other?

	The only files the rush install modifies outside of the rush
	directory is the rush boot script, and adding rush/bin to the PATH
	of the csh and sh startup files.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)


Last Next