Hm, maybe my explanation was a little confusing, sorry. I don't need to know
how to tell Nuke the environment variable. I know that for the Finder and the
terminal version. That's working fine.
My Problem is: Nuke doesn't recognize/respect the environment variable after
the first successful launch of Nuke! Even if you delete the environment
variable, if you change it to another value, etc., Nuke will just ignore it and
will use the first value you set it to forever! So you can't change the
licensing of an installed Nuke on OS X after the first launch. Nuke
caches/stores this value somewhere and I just can't find out where.
Testing the same thing on our windows machines shows a behaviour that is the
expected behaviour: if you change the value of LM_LICENSE_FILE, it will respect
this every time you start Nuke and will behave accordingly. For example: if you
change LM_LICENSE_FILE to or delete it, Nuke will show the error message
about the missing license file. If you do the same on OS X, Nuke will just
start fine without the error message and it grabs a floating license from the
license server that were defined when started it for the first time.
So I'm trying to find the file/location where Nuke stores/caches this value.
Abraham
Am 15.09.2011 um 21:28 schrieb Deke Kincaid:
bashrc, tcshrc, login, profile, etc... set environment variables are
not seen by the gui. You should set it in either in an
environment.plist file or /etc/launchd.conf. Launchd is the only
thing that is seen by everything in the system, environment.plist is
ignored if you launch apps from spotlight.
There is a gui for launchd called Lingon
http://www.peterborgapps.com/lingon/
There is a nice little gui for setting environment.plist in the system
preferences called RCEnvironment.
http://www.rubicode.com/Software/RCEnvironment/
-deke
On Thu, Sep 15, 2011 at 03:35, Abraham Schneider aschnei...@arri.de wrote:
Hi there!
I discovered a strange behaviour of Nuke on OS X:
Install Nuke on a Mac and have a license server running with floating
licenses of Nuke. Now create a new user and try to start nuke from the
terminal. Nuke will startup with the message window mentioning that it
can't find the license file.
Now do as the message says and create a new environment variable
called LM_LICENSE_FILE and give it the path to a file where you define
the license server. If you now start Nuke from the terminal, it just
starts fine like it should do.
Strange thing is: if you close your terminal window and start a new
one where you DON'T have the environment variable LM_LICENSE_FILE set
correctly, it will start nevertheless. Nuke doesn't need the
environment variable ever again for this user. So it seems like Nuke
stores the information about the license server somewhere in the user
folder.
Anyone knows where Nuke stores this information and why? Does it make
sense to have an environment variable and not using it every time you
start Nuke?
Thanks, Abraham
Abraham Schneider
Senior VFX Compositor
ARRI Film TV Services GmbH
Tuerkenstr. 89
D-80799 Muenchen / Germany
Phone +49 89 3809-1269
EMail aschnei...@arri.de
www.arri.de/filmtv
Abraham Schneider
Senior VFX Compositor
ARRI Film TV Services GmbH
Tuerkenstr. 89
D-80799 Muenchen / Germany
Phone +49 89 3809-1269
EMail aschnei...@arri.de
www.arri.de/filmtv
ARRI Film TV Services GmbH
Sitz: München Registergericht: Amtsgericht München
Handelsregisternummer: HRB 69396
Geschäftsführer: Franz Kraus, Dr. Martin Prillmann, Josef Reidinger
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
