Re: [exim] 'sudden' appearance of "failed socket bind()"

hi sander & tony,

-- On September 13, 2005 9:17:57 AM +0200 Sander Smeenk <ssmeenk@???>
wrote:
> I'm not completely sure, but my guess would be that your exim is now
> dropping its privileges after it started. You start it as root, but it
> runs as another user.
>
> Binding to a port <1024 requires root privileges, so HUP'ing the daemon
> will close the socket and try to reopen it, but it is then running as
> the non-privileged user (which is actually a good thing(TM)). Binding to
> 'privileged ports' is then prohibited.

-- On September 13, 2005 10:56:05 AM +0100 Tony Finch <dot@???> wrote:
>> ok, i've done something stupid ... and can't for the life of me figure out
>> what.
>
> You've lost the setuid bit from your Exim binary.

it turns out that suid on the binary itself was, per your comments, the problem.

i honestly have NO idea how/why it occurred -- other than the distinct
possibility that i inadvertently changed something ...

so, to play it safe in case i munged something else as well, i wiped my app
dir, and did a complete/fresh reinstall, rather than an overwrite.

all is, once again, working perfectly.

thx!

cheers,

richard