From: matx <matx@(email surpressed)> Subject: Shake 4.1 and Rush Date: Mon, 21 Aug 2006 10:34:05 -0400 |
Msg# 1374 View Complete Thread (3 articles) | All Threads Last Next |
Hi Are there any issues with the new Shake 4.1 and Rush?We've just upgraded and users are complaining of no longer being able to network render, while rendering locally works. I'll investigate more fulyl when I am back in the office, but I wanted to see if anything is known beforehand. We're using MacOSX 10.4.7, Shake 4.1, GenArts Sapphire v.2 plugins with a license server. Thanks, Mat X |
From: Greg Ercolano <erco@(email surpressed)> Subject: Shake 4.1 and Rush Date: Mon, 21 Aug 2006 16:11:29 -0400 |
Msg# 1375 View Complete Thread (3 articles) | All Threads Last Next |
You followed up in private email with this error from the plugin: INIT_Processeses(), could not establish the default connection to the WindowServer.Loaded Sapphire Plug-ins v2.0 for Shake 4.10. Sounds like the plugin is trying to access the OSX window manager (which is what the above error means), and that's bad. Short answer is probably to just make the shake executable setuid root: chown 0:0 /path/to/shake/bin/shake chmod 4755 /path/to/shake/bin/shake (This obviously has local security implications) This is the same solution we use to "fix" AfterEffects, which by default tries to always access the window manager. Command line renders should NOT be trying to do anything to the window managers. Neither should their plugins (when running in a command line rendering mode) My guess is the plugin is either invoking a window manager system call, or causing a 3rd party library to be loaded whose initialization code is trying to connect to the window manager. The plugin guys can probably replicate if they 'ssh' into their own mac workstation as a different user than the user currently logged into the window manager, and try to invoke a command line render to run. -- Greg Ercolano, erco@(email surpressed) Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed) Fax: (Tel# suppressed) Cel: (Tel# suppressed) |
From: Mathieu Xavier Mauser <mathieuxaviermauser@(email surpressed)> Subject: Re: Shake 4.1 and Rush Date: Mon, 21 Aug 2006 17:17:42 -0400 |
Msg# 1376 View Complete Thread (3 articles) | All Threads Last Next |
Greg,I would just add that this is now an acknoledged bug in the v.2 (SapphireShakeInstall-2.0s41.pkg) of the GenArts Sapphire plugin for MacOSX. Just one of several bugs I confirmed, so far. The first bug pulled up a root-owned window over the "login window" during the remote install. Then it did not see the license server, and instead involed a demo/trial mode, and 3rd when no user was logged in, then the renders fail with RUSH. All errors should be corrected in a newer version of the installer, I am told. Now that they know about these issues. Mat X On 2006-08-21 13:11:29 -0700, Greg Ercolano <erco@(email surpressed)> said: You followed up in private email with this error from the plugin:INIT_Processeses(), could not establish the default connection to the WindowServer.Loaded Sapphire Plug-ins v2.0 for Shake 4.10.Sounds like the plugin is trying to access the OSX window manager (which is what the above error means), and that's bad. Short answer is probably to just make the shake executable setuid root: chown 0:0 /path/to/shake/bin/shake chmod 4755 /path/to/shake/bin/shake |