Hello,

Fatima Mojaddidy wrote: > Hello SysAdmins, > > What are some of the ways you handle running multiple versions of Maya and > environment variables for Maya (in a Linux setup)? I'm trying to figure out > what the best way will be.

You could try environment modules. http://modules.sourceforge.net/

Best, Dave

-- David Bertram, Graphics Systems Manager The Ohio State University Advanced Computing Center for the Arts and Design 1224 Kinnear Rd., Rm 231 Columbus, OH 43212-1154 Voice: 614.292.1041

interesting thanks =)

Hello Fatima,

Pointing the maya.env fiile to respective version of Maya startup/scripts directory .

In the Maya.env file set MAYA_SCRIPT_PATH to the location of? mel scripts

?'/home/username/maya/Maya.env' or '/home/username/maya/2010-x64/Maya.env' should contain the line:

MAYA_SCRIPT_PATH=<path to directory containing startup.mel>

i.e.:

MAYA_SCRIPT_PATH=/path/to/the/scripts/with-respect-to-maya-version


Similarly have respective versions of Maya environment pointing to respective scripts directory. This would keep the configuration and plugins separate with respect to the versions of maya being used.

Reference: http://download.novedge.com/Brands/Alias/Helps/Maya6.5/en_US/Env/filepathvariables.html

Cheers,
Adarsh
http://www.linkedin.com/in/adarsh

Hello,

Rangi Sutton wrote: > On 9 March 2010 06:47, David Bertram dbertram@accad.ohio-state.edu wrote: > >> Hello, >> >> >> Fatima Mojaddidy wrote: >> >>> Hello SysAdmins, >>> >>> What are some of the ways you handle running multiple versions of Maya and >>> environment variables for Maya (in a Linux setup)? I'm trying to figure >>> out >>> what the best way will be. >>> >> You could try environment modules. >> http://modules.sourceforge.net/ >> >> > > Ah.. can't believe I've never even searched for a tool like that. Looks very > interesting. Are folks using this? I see one advantage being that ops can

It's largely in use in big cluster installations.

choose the shell they use, maybe a customised bootstrapping script that's shell specific but just starts calling module commands.

Is this the case in practise?

Yes. You can use .cshrc/.login/.bashrc files.

It also looks like it could clean up a bunch of stuff render-farm side, where you want to recreate or inherit the environment a job was submitted from.

Has anyone got a real-world example of these tcl config files that module reads, for maya for instance?

Not for Maya, but, a real world tcl example for mpi:

%Module

note that this is read by a Tcl interpretor

Grabbed from the docs ''' (Linux(r))

 ~/maya/version
 ~/maya
  Note
      o Make sure to capitalize Maya.env.
      o On Windows and Linux, you can change the location where Maya

looks for Maya.env by setting the MAYA_APP_DIR environment variable using the operating system methods described below. '''

So within your user home for you renderer user, you have each version. You can individually set the maya.envs of each version independently of each other. For ease of management point user home directory to shared filespace and only make the changes once.

Hope that helps

-----Original Message----- From: studiosysadmins-discuss-bounces@mailman.studiosysadmins.com [mailto:studiosysadmins-discuss-bounces@mailman.studiosysadmins.com] On Behalf Of David Bertram Sent: Tuesday 09 March 2010 15:05 To: discuss@studiosysadmins.com Subject: Re: Multiple versions of Maya and environment variables

Hello,

Rangi Sutton wrote: > On 9 March 2010 06:47, David Bertram dbertram@accad.ohio-state.edu wrote: > >> Hello, >> >> >> Fatima Mojaddidy wrote: >> >>> Hello SysAdmins, >>> >>> What are some of the ways you handle running multiple versions of Maya and >>> environment variables for Maya (in a Linux setup)? I'm trying to figure >>> out >>> what the best way will be. >>> >> You could try environment modules. >> http://modules.sourceforge.net/ >> >> > > Ah.. can't believe I've never even searched for a tool like that. Looks very > interesting. Are folks using this? I see one advantage being that ops can

It's largely in use in big cluster installations.

choose the shell they use, maybe a customised bootstrapping script

that's > shell specific but just starts calling module commands. > > Is this the case in practise?

Yes. You can use .cshrc/.login/.bashrc files.

It also looks like it could clean up a bunch of stuff render-farm

side, > where you want to recreate or inherit the environment a job was submitted > from. > > Has anyone got a real-world example of these tcl config files that module > reads, for maya for instance?

Not for Maya, but, a real world tcl example for mpi:

%Module

note that this is read by a Tcl interpretor