On Fri, Nov 06, 2020 at 09:59:46PM +, isdtor wrote:
This is MIT KRB5 1.10. I've tried this on systems with newer versions,
too, with the same result. I am not aware of any configuration specific
to GSSAPI, only Kerberos (and I have a valid ticket).
I'll have to punt on this for now then.
On Fri, Nov 06, 2020 at 11:22:18PM +0100, Matthias Apitz wrote:
El día viernes, noviembre 06, 2020 a las 10:02:46a. m. -0800, Ian Zimmerman
escribió:
So, does mutt set SIG_IGN for SIGCHLD? Maybe it should not, or maybe it
should temporarily restore it in places like this where it synchronously
El día viernes, noviembre 06, 2020 a las 10:02:46a. m. -0800, Ian Zimmerman
escribió:
> On 2020-11-06 08:25, Matthias Apitz wrote:
>
> > See also man page of wait(2): the errno=ECHILD:
>
> >ECHILD (for waitpid() or waitid()) The process specified by pid
> >(waitpid()) or idtype
> At this point, I'm just guessing, as I have almost no experience with
> Kerberos. The message above may supply some kind of clue: Server not
> found in Kerberos database. Which GSSAPI library is SASL using? Is it
> possible there is some setup or configuration that library needs to
> fun
On 2020-11-06 08:25, Matthias Apitz wrote:
> See also man page of wait(2): the errno=ECHILD:
>ECHILD (for waitpid() or waitid()) The process specified by pid
>(waitpid()) or idtype and id (waitid()) does not exist or is
>not a child of the calling process. (This can happe
