19 Jul
2005
19 Jul
'05
8:44 a.m.
On Mon, 18 Jul 2005, Michael Ulitskiy wrote:
and now ser doesn't start. Actually "log_stderror=no" is the setting that causes problem. If it's set to "yes", ser starts fine even in forked mode. Also I narrowed down the problem to postgres module. If I remove it from ser.cfg then ser starts as it should.
See, http://lists.iptel.org/pipermail/serdev/2005-July/005148.html
I guess postgres could be multi-threaded.
Guys, isn't it time to make (as described in the referenced message) SER more friendly to multi-threaded third-party libraries?
--
...Bye..Dmitry.