Thanks all. I'll try to get this method running. On Sun, Dec 18, 2011 at 4:34 AM, Johannes Hezer <[email protected]>wrote:
> I think it should like this : > > #!/bin/bash > > export NUKE_PATH="/test" > open /Applications/Nuke6.3v1/Nuke6.3v1.app > > you can save this as a .command on your server, so you only have to edit > this file and then make an alias to the workstations and if you launch this > I think you should be fine.. > > -johannes > > > Am 12/18/11 12:32 AM, schrieb Tim BOWMAN: > > > On Sun, Dec 18, 2011 at 6:39 AM, Nathan Rusch <[email protected]>wrote: > >> >> However, I would probably go one step further and say ditch the >> environment.plist, and instead opt for setting up your shell environment >> purely via ~/.bash_profile or some other more "standard" approach. >> >> > I'm with Nathan here, except I'd recommend doing it on the system level > in /etc/bashrc so it gets loaded for any user in any (bash) shell, whether > it's login or not. I did a bunch of googling while I was putting together a > job environment system for myself ( > https://github.com/timbowman/OpenSourcePipeline) and this page was the > best I found for helping me understand the whole profile thing: > > http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html > > > _______________________________________________ > Nuke-users mailing [email protected], > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > -- Gary Jaeger // Core Studio 249 Princeton Avenue Half Moon Bay, CA 94019 650 728 7060 http://corestudio.com
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
