[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
OK, so I've been running downloading all my email to my server and getting it via imap for the past few months. Works great. Except that the other day it stopped working. Not quite sure why. Anyhow restarting courier-imap fixed it. Well, it would have, except that I then spent ages trying to figure out why it wouldn't start properly. It turns out that for some reason famd had bound itself to the imaps port. Why on earth did it do that? Failing to remember why famd was running in the first place I stopped it, restarted courier-imap, and everything was fine again. Until just now, when for some reason I couldn't copy email to the sent folder. Looking in my logs I see that courier-imap is complaining about the lack of fam, and had been ever since it was restarted. Funny- I'm sure I'd sent email before. Anyway I started famd (which didn't complain that courier-imap had the imaps port) and everything was fine again. No more complaints in the logs. So: Firstly, why on earth did famd bind to the imaps port? Secondly, why on earth did famd bind to the imaps port? Thirdly, do I really need famd, and if I do, how do I stop it from doing that again? Thanks Simon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html