Linux NUKE_PATH Environment Variable only regonized in GUI / Interactive












0














I have set the "NUKE_PATH" environment variable which is recognized and loads without issue when running nuke from an open terminal but when I submit a remote render job using RUSH, it is being ignored.



Even running Nuke in -V verbose mode from the terminal shows where it loads the environment variable and looking at the logs, that's being skipped when submitting remotely.



I have set the NUKE_PATH in the following 3 places:




  • /etc/environment (NUKE_PATH=/path/to/scripts)

  • ~/.bashrc (export NUKE_PATH='/path/to/scripts')

  • ~/.bash_profile (export NUKE_PATH='/path/to/scripts')


None of these are being recognized with a command line execution of a render but all work fine in the GUI.



Any help would be greatly appreciated.










share|improve this question









New contributor




tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0














    I have set the "NUKE_PATH" environment variable which is recognized and loads without issue when running nuke from an open terminal but when I submit a remote render job using RUSH, it is being ignored.



    Even running Nuke in -V verbose mode from the terminal shows where it loads the environment variable and looking at the logs, that's being skipped when submitting remotely.



    I have set the NUKE_PATH in the following 3 places:




    • /etc/environment (NUKE_PATH=/path/to/scripts)

    • ~/.bashrc (export NUKE_PATH='/path/to/scripts')

    • ~/.bash_profile (export NUKE_PATH='/path/to/scripts')


    None of these are being recognized with a command line execution of a render but all work fine in the GUI.



    Any help would be greatly appreciated.










    share|improve this question









    New contributor




    tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0







      I have set the "NUKE_PATH" environment variable which is recognized and loads without issue when running nuke from an open terminal but when I submit a remote render job using RUSH, it is being ignored.



      Even running Nuke in -V verbose mode from the terminal shows where it loads the environment variable and looking at the logs, that's being skipped when submitting remotely.



      I have set the NUKE_PATH in the following 3 places:




      • /etc/environment (NUKE_PATH=/path/to/scripts)

      • ~/.bashrc (export NUKE_PATH='/path/to/scripts')

      • ~/.bash_profile (export NUKE_PATH='/path/to/scripts')


      None of these are being recognized with a command line execution of a render but all work fine in the GUI.



      Any help would be greatly appreciated.










      share|improve this question









      New contributor




      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I have set the "NUKE_PATH" environment variable which is recognized and loads without issue when running nuke from an open terminal but when I submit a remote render job using RUSH, it is being ignored.



      Even running Nuke in -V verbose mode from the terminal shows where it loads the environment variable and looking at the logs, that's being skipped when submitting remotely.



      I have set the NUKE_PATH in the following 3 places:




      • /etc/environment (NUKE_PATH=/path/to/scripts)

      • ~/.bashrc (export NUKE_PATH='/path/to/scripts')

      • ~/.bash_profile (export NUKE_PATH='/path/to/scripts')


      None of these are being recognized with a command line execution of a render but all work fine in the GUI.



      Any help would be greatly appreciated.







      linux command-line environment-variables centos-7 rendering






      share|improve this question









      New contributor




      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 2 days ago







      tbutton













      New contributor




      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 days ago









      tbuttontbutton

      12




      12




      New contributor




      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Upon further experimentation, I found the best way to handle this wasn't at blade level in linux but rather at submission level with python. Setting ENV as part of the process with:




          • os.environ["NUKE_PATH"] = "/path/to/scripts"


          fixes the problem and handles it in a more controlled and efficient way while also saving the hassle of having to set ENV on any of the host machines no matter what OS it is.






          share|improve this answer








          New contributor




          tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });






            tbutton is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390790%2flinux-nuke-path-environment-variable-only-regonized-in-gui-interactive%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Upon further experimentation, I found the best way to handle this wasn't at blade level in linux but rather at submission level with python. Setting ENV as part of the process with:




            • os.environ["NUKE_PATH"] = "/path/to/scripts"


            fixes the problem and handles it in a more controlled and efficient way while also saving the hassle of having to set ENV on any of the host machines no matter what OS it is.






            share|improve this answer








            New contributor




            tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.























              0














              Upon further experimentation, I found the best way to handle this wasn't at blade level in linux but rather at submission level with python. Setting ENV as part of the process with:




              • os.environ["NUKE_PATH"] = "/path/to/scripts"


              fixes the problem and handles it in a more controlled and efficient way while also saving the hassle of having to set ENV on any of the host machines no matter what OS it is.






              share|improve this answer








              New contributor




              tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                0












                0








                0






                Upon further experimentation, I found the best way to handle this wasn't at blade level in linux but rather at submission level with python. Setting ENV as part of the process with:




                • os.environ["NUKE_PATH"] = "/path/to/scripts"


                fixes the problem and handles it in a more controlled and efficient way while also saving the hassle of having to set ENV on any of the host machines no matter what OS it is.






                share|improve this answer








                New contributor




                tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                Upon further experimentation, I found the best way to handle this wasn't at blade level in linux but rather at submission level with python. Setting ENV as part of the process with:




                • os.environ["NUKE_PATH"] = "/path/to/scripts"


                fixes the problem and handles it in a more controlled and efficient way while also saving the hassle of having to set ENV on any of the host machines no matter what OS it is.







                share|improve this answer








                New contributor




                tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 2 days ago









                tbuttontbutton

                12




                12




                New contributor




                tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                tbutton is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






















                    tbutton is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    tbutton is a new contributor. Be nice, and check out our Code of Conduct.













                    tbutton is a new contributor. Be nice, and check out our Code of Conduct.












                    tbutton is a new contributor. Be nice, and check out our Code of Conduct.
















                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390790%2flinux-nuke-path-environment-variable-only-regonized-in-gui-interactive%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?