Alex:
> Hi,
>
> >> For reference, there was nothing further in the system or postfix
> >> logs, dmesg, or even by increasing the postfix logging level to the
> >> best of my ability.
> >
> > When the kernel reports "Resource temporarily unavailable", that's
> > all that Postfix can report without second-guessing the kernel.
>
> Yes, understood. I was more referring to having postfix better
> indicate what it was trying to do that caused the error, but I guess
> that's clear to me now that it was trying to change user IDs.
When postsuper asked the kernel to execute setuid(103), that request
failed with "Resource temporarily unavailable". There is no need
to explain the purpose of setuid(), or why postsuper asked the
kernel to execute setuid(103), because the blame for setuid()
failure is never with postsuper, just like one should not blame
the messenger for bringing bad news. In this particular case, the
kernel policy was too restrictive for Postfix's requirements.
Wietse
