Subject: Re: sh: internal error: setexecsig: unset signal 0((null %s))
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 02/19/2004 15:13:45
In article <20040219145910.GA16009@colwyn.zhadum.de>,
Matthias Scheler <email@example.com> wrote:
>when I start "mutt" on my NetBSD-current system I can several of these
>errors (probably when "mutt" launches "sh" from my ".muttrc"):
>sh: internal error: setexecsig: unset signal 0((null %s))
>Does anybody know what goes wrong here? It seems not to be related to
>"/bin/sh" because a NetBSD 1.6.2 "/bin/sh" doesn't fix the problem.
This is not an sh bug; the string does not appear in the sh binary. Perhaps
your /bin/sh is /bin/ksh?