On 1/1/2017 1:38 PM, Gaja Sophie Peters wrote: > I wonder if this problem is related to the matlab "bug" (a little > off-topic maybe, but who knows) Matlab simply won't start from a > directory with @sys in the path, so one has to specifically go via > amd64_linux26 (or whatever is appropriate). Since it's just "luck", > which path to the final directory the kernel sees first (depending on > what else got called in what order), sometimes Matlab won't even start > from amd64_linux26 because it STILL thinks, it's called from @sys -- > whatever the kernel sees first, it remembers and will continue to > remember until a reboot...
I'm curious about this "matlab" incompatibility. Can you clarify what
you mean by "a directory with @sys in the path"? Do you mean:
1. a path component "@sys" is being passed to Matlab?
/afs/cell-name/appl/@sys/bin/prog
2. a path component that is a symlink whose target path
contains @sys?
/afs/cell-name/appl/bin/prog
where "bin" is a symlink to "@sys" or to ".bin/@sys"
where ".bin" is a directory containing sub-directories
"amd64_linux26".
Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
