ni...@lysator.liu.se (Niels Möller) skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> (This is due to the Guix setup where by default nothing would be found >> in $PATH; patch attached. > > That's a pretty non-standard environment... > > Processes spawned for a user by lshd get a pretty trimmed down initial > environment, with PATH set to /bin:/usr/bin or something close. If > standard unix tools aren't found there, then I think you'd need to > either > > * have the shell startup files setup a working path (ssh "shell" is > implemented by spawning a login shell, and "exec" by starting a shell > with -c command-line-string). > > * Or some option to lshd to let child processes inherit PATH or set it > to a specific value. Not sure if it's appropriate to use that when > running the tests, though. There's a related hack to inherit HOME in > some circumstances.
On GuixSD we now use ‘pam_env’ to address the issue of initializing PATH, and before that we had /etc/profile do the right thing. So this is fine. In the test environment, we cannot rely on this, though. So I think the only viable options are the patch I posted, or inheriting PATH as you suggest (but that option should be used for testing only IMO.) WDYT? Thanks, Ludo’. _______________________________________________ lsh-bugs mailing list lsh-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
