tag:blogger.com,1999:blog-14427379.post112586564707592135..comments2023-05-30T15:20:21.068+02:00Comments on The Core Dump of Thought: Bitlbee encrypted storage patchzvrbahttp://www.blogger.com/profile/08806965334872601252noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-14427379.post-7244095605996826192007-11-17T14:50:00.000+01:002007-11-17T14:50:00.000+01:00(Wow, it took me two years to find this post..)Thi...(Wow, it took me two years to find this post..)<BR/><BR/>This is when it fails to set up an IM-connection? Two years passed now, so I hope this was resolved.<BR/><BR/>Anyway, about the OpenSSL issue: This isn't something we chose for. I once asked a Gaim developer for permission to use OpenSSL and it was denied. Remember that BitlBee contains a lot of (well, not as much these days as it used to) third-party code which we don't own and can't relicense.<BR/><BR/>BTW, what do you think of the new .xml file format?Wilmer van der Gaasthttps://www.blogger.com/profile/14588872074963049785noreply@blogger.comtag:blogger.com,1999:blog-14427379.post-1125931248767564262005-09-05T16:40:00.000+02:002005-09-05T16:40:00.000+02:00Actually, the problem is exactly as I've described...Actually, the problem is exactly as I've described it - when run from inetd.<BR/><BR/>If run as a single-process daemon, it will overflow <I>per-process</I> fd limit much sooner than the system-wide limit and no harm to the system will come.<BR/><BR/>When run from inetd, many clients can connect, each having its own, long-lasting process instance of bitlbee. And together they will overflow the <I>system-wide</I> limit of open files.zvrbahttps://www.blogger.com/profile/08806965334872601252noreply@blogger.comtag:blogger.com,1999:blog-14427379.post-1125911289822097012005-09-05T11:08:00.000+02:002005-09-05T11:08:00.000+02:00Just a correction - you said:"If spawned from inet...Just a correction - you said:<BR/>"<I>If spawned from inetd, it is trivial to overflow the system's file descriptor table.</I>"<BR/>Actually the leakage is a problem<BR/>when running it as a standalone<BR/>daemon. If spawned from inetd, the<BR/>server exits upon serving one<BR/>client, so the leaked fd would be<BR/>reclaimed immediately by the operating system.Senkohttps://www.blogger.com/profile/02871690938716392627noreply@blogger.com