Hello Ralf,
In /usr/local.nfs/Modules/latest/init/bash, there should be a line like:
eval "$(${_mlre:-}/usr/bin/tclsh
'/usr/local.nfs/Modules/5.2.0/libexec/modulecmd.tcl' bash autoinit)"
Could you change it into something like:
eval "$(${_mlre:-}/usr/bin/tclsh
'/usr/local.nfs/Modules/5.2.0/libexec/modulecmd.tcl' bash -D autoinit
2>modules_autoinit_debug.log)"
And send me the modules_autoinit_debug.log file that will be produced
after trying to connect with NoMachine.
Regards,
Xavier
Le ven. 24 mars 2023 à 11:58, Aumüller, Ralf
<Ral...@ip...> a écrit :
>
> Hello,
>
> after updating from 5.1.1 to 5.2.0 we have the following problem:
>
> - When logging in via SSH, everything works as expected
>
> - When I try to connect per NoMachine client I get an error from Nomachine.
> Locking in the logs and doing some debugging it appears that the following
> init-command ". /usr/local.nfs/Modules/latest/init/bash" removes the default
> paths from PATH. Before the command is executed the PATH is
> "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin". After the
> command PATH is just "/usr/local.nfs/Modules/5.2.0/bin". And then the rest of
> our setup fails and NoMachine fails to.
>
> Any idea whats wrong?
>
> Thank You and best regards,
> Ralf
>
>
> Info:
> - OS is Ubuntu 20.04
> - Self-compiled modules
> - Our self-compiled modules are installed below /usr/local.nfs/Modules as e.g.
> 5.2.0 or 5.1.1. The symlink latest points to the module-version to execute.
>
>
> _______________________________________________
> Modules-interest mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/modules-interest
|