On Tue, May 19, 2009 at 05:37:12PM -0400, Ed Blackman wrote: > I have a cron process that regularly runs "mairix 2>&1 | egrep -v '(could > not.*parse|Can't (find|process).*boundary)'" > > Occasionally (a couple times a week at maximum, out of roughly 1000 > times per week that it runs), I get: > > mtime failed for '/home/edgewood/mail/archive/20179' > mtime failed for '/home/edgewood/mail/archive/20180' > > I've glanced at the code and found where that message is generated, but > don't understand enough of the context to determine what causes the > message, and whether I can safely ignore it. So what does cause it, and > can I ignore it?
In a folder of type MH or maildir (MH in your case I guess), this message is generated when the modification time of one of the files has changed since the last scan. If this condition occurs, mairix will rescan the file, since the contents may have changed in some way. The message is benign and was a remnant of my debugging of the early implementation that has been left in for longer than planned. I have removed the fprintf call now. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Mairix-users mailing list Mairix-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mairix-users
