Author: Phil Pennock Date: To: Cyborg CC: <exim-users@exim.org> Subject: Re: [exim] Exim appears to stop handling mail via the localuser
router after a while
On 2013-05-19 at 15:30 +0200, Cyborg wrote: > Am 18.05.2013 04:54, schrieb Phil Pennock:
> > The problem claimed is not that the user can't access the files, or
> > that the uid/gid can't be figured out frm the name, but that the
> > gid/uid can not be set by the running process. That's entirely a
> > kernel constraint. Which leads to "what could make that fail?". Well,
> > it will fail if you lack permission to make the transition. You can
> > lack permission if you're not root, or capabilities are preventing the
> > action. As long as Exim is
>
> A permission problem would happen everytime, not after 3 hours running
> without fail.
No, filesystem problems can change what's visible to a process. If it's
a normal, robust and well tested, filesystem on local disk, then that's
almost certainly not the cause. If it's an experimental filesystem or a
network filesystem, then state desynchronisation and cache corruption of
the filesystem metadata becomes more plausible.
> The inode hint wasn't bad. If the quota isn't full and no tempfile
> eating the diskspace, a low running inode problem could be the reason.
No, a lack of new inodes will not affect the visible attributes of an
existing inode, so that could not be the reason.
