Actions
Bug #13557
closedpf[k]sh fails to properly resolve paths
Start date:
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
Description
Following the update to ksh93u+ in #13405, the ksh profile shells fail to properly resolve paths. This bug appears to mostly manifest in a non-global zone, and only if the profile shell is started with an absolute path.
Reproducible test case from Brian Bennett:
#!/usr/bin/pfksh # This will fail ls -1 / | head -1 # This will succeed /bin/ls -1 / | head -1
In an OmniOS bloody global zone, it works:
bloody% ./bahksh HVMamirpool HVMamirpool
and in a NGZ, it fails:
root@sparse:~# /bahksh pfexec: unable to execute : No such file or directory bahksh
and, interactively, it only fails if the interpreter is started with an absolute path:
root@sparse:~# pfksh u@h:w$ ls -l | head -1 total 0 u@h:w$ /bin/ls -l | head -1 total 0 root@sparse:~# /usr/bin/pfksh u@h:w$ ls -l | head -1 pfexec: unable to execute : No such file or directory u@h:w$ /bin/ls -l | head -1 total 0
Actions