If your licenses have multiple maintenance dates, sometimes multiple Nuke instances (or maybe NukeX stuff?) can end up taking a second license
If "lmstat -i" lists multiple versions of nuke_i, that's likely the problem.. support@ should be able to help, there's clever rearranging of licenses that might help ..unless it's something completely different On 18/11/11 07:13, ross daly wrote: > I'm having a problem where one machine will sometimes end up taking > multiple nuke licenses. Opening a script from the os file browser will > lock up another license, but opening it from within nuke will not. > > I can check the license server to see who the offending party is, but > how do I prevent it from happening? We are running Win 7 and nuke 6.3v2. > > http://learningnuke.com > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users -- ben dickson 2D TD | [email protected] rising sun pictures | www.rsp.com.au _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
