Hi,
>
> IIRC pdksh seemed to work in my sid box, while ksh not. However I am not now
> at
> that box. Trying again here in an etch box pdksh fails. I will try again in a
> sid
> box when possible. I may have messed up the names with all the sh changes.
>
There were similar bug in pdksh reported few years ago (#154540). I
fixed it by applying patch from OpenBSD, so now pdksh when called as
pdksh does set close-on-exec, and when called as sh doesn't.
There's a following comment in pdksh source code:
/*
* For ksh keep anything > 2 private,
* for sh, let them be (POSIX says what
* happens is unspecified and the bourne shell
* keeps them open).
*/
However I have never checked if it's true that POSIX doesn't specify what
happens in this case. But if it is, debconf should be fixed not to use
such constructions, I think.
Regards,
Robert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
