Bug #13557
Updated by Andy Fiddaman 8 months ago
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 start with an absolute path. Reproducible test case from Brian Bennett: <pre> #!/usr/bin/pfksh # This will fail ls -1 / | head -1 # This will succeed /bin/ls -1 / | head -1 </pre> In an OmniOS bloody global zone, it works: <pre> bloody% ./bahksh HVMamirpool HVMamirpool </pre> and in a NGZ, it fails: <pre> root@sparse:~# /bahksh pfexec: unable to execute : No such file or directory bahksh </pre> and, interactively, it only fails if the interpreter is started with an absolute path: <pre> 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 </pre>