I'll double check later when I can get to an SSH session, but I don't think
this is the answer.
There are four or five different builds of exim in /usr/exim/bin and only the
current one (the one symlinked to as "exim", hmm...) was affected. Also,
everything has been running *just fine* for around 6 months, so why now all
of a sudden?
Regrettably in my haste to fix the problem I forgot to make a note of the
file modification date. That would have given me a clue as to whether this
was by "design" or perhaps (as I'm inclined to suspect as this box has
done "odd" things before) a hardware issue.
Many thnks for your input though Peter.
Phil
On Mon, 22 Nov 2004 09:05:25 +0000, Peter Bowyer wrote
> On Mon, 22 Nov 2004 08:29:11 +0000, Phil Jordan
> <exim-user@???> wrote:
> > Yes Marc you're absolutely right that is what had happened.
> >
> > A quick chmod and all returned to normal.
> >
> > Hmmm.... file system errors. Not good.
>
> Some flavours of Linux have a cron job which wakes up every so often
> and silently messes with suid bits, generally to the detriment of
> running software. Maybe you feel foul of one of these? I believe they
> can be persuaded that th exim binary is something which can be
> trusted with a suid bit, but I've no idea how.
>
> Peter
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim
details at
http://www.exim.org/ ##
