On 6 Dec 2018, at 12:13, Dominic Raferd wrote:
On Thu, 6 Dec 2018 at 16:37, Bill Cole <
postfixlists-070...@billmail.scconsult.com> wrote:
On 6 Dec 2018, at 11:15, Dominic Raferd wrote:
Have you verified that the inode number changes?
no, I will check how to do this
'ls -li' is your friend.
Thanks, I have now used this to confirm that the inode number does not
change when postfix/local updates the mbox file. So the problem with
incrond lies elsewhere.
One thing to check is the sysctl parameter 'fs.inotify.max_user_watches'
(which is what its name implies.) Some (EL-family, for example)
distributions default to a low value (8K) which is a very easy limit to
hit with a tool like incron that is designed to exploit inotify to its
fullest.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
