After successful Deadline installation both manually and through salt on Linux machine, there is missing DEADLINE_PATH from the terminal. Does anyone have any idea what could be causing this?
I’m not sure it does set it?
https://docs.thinkboxsoftware.com/products/deadline/10.3/1_User%20Manual/manual/quick-install-client.html#linux
I’ve been installing it centrally with rhel7/8/9 installs and adding the path in when required, I’ll see if I can run a local install and check it set this.
Is it possibly installing the env var as the user installing?
I checked, did a local install on a VM
adds env var for both root and user, I had to launch a new shell for it to show though
I am Dobri’s colleague, and the weird thing is that on my machine the variable is set, and on his it is not. We use the exact same installation procedures. I think only Ubuntu version is different, which may be significant.
On a more basic level, we could not figure out the mechanism by which the variable is set - it is not in /etc/environment, in .bashrc, .profile, pam_env.conf, systemd deadline service… So how does it exist at all?
1 Like
This maybe an OS change thing, think there’s still different installers everywhere sticking things all over the place! systemd etc… often find myself aligning stuff to the newer method!
I checked where I thought it was on this vanilla vm, and sure enough it was there, I often set things here (/etc/profile.d/custom.sh) that don’t get picked up when things are running as a service (skipping .bash_profile etc)
1 Like
That’s it, thank you! Can’t believe I missed this place. Now going to figure out why it’s not happening in 24.04
1 Like