> I think the extra imapd processes you're seeing are the result of a separate
> issue all together. Most IMAP clients tend to open multiple sessions.
> Usually so they can keep track of new arrivals in INBOX while working on
> different folders. These aren't forked. They are separate invocations run
> by ?inetd for new and different network requests.
>
> I remember a few years back dealing with a customer site that used Outlook.
> That version of outlook would open a connection to the mail server for
> _every_ folder the user had recently opened. Some of the heavier users were
> using 20+ simultaneous imapd processes.
Actually, I was getting something else confused.
I already knew about the Outlook problem, and wasn't referring to it.
In my earlier email when I mentioned the load due to fork()ing, I was
only talking about what you'd expect to result from clients
connecting and disconnecting. With enough users, I thought perhaps this
load becomes non-negligible.
When Mark responded with details about the conditions under which imapd
forks, I forgot that the forking I was originally referring to is due
to inetd!
Thanks for pointing it out. :)
Cheers,
- Joel
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
