From: Pawel J. D. <ni...@ga...> - 2003-06-21 07:03:43
|
On Fri, Jun 20, 2003 at 05:43:06PM -0700, Dariusz Kulinski wrote: +> I recently noticed some strange problems while cerber 1.0 RC2 is +> loaded (I didn't saw them in RC1). +>=20 [...] +> Bus error (core dumped) There could be an error in mechanism that was implemented in cerb RC2. In cerb RC1 was race condition in arguments handling. I've eliminate it. You can read about this in commitlog at: http://sourceforge.net/mailarchive/forum.php?thread_id=3D2051245&forum_id= =3D9483 Bus error can occur when someone is trying to check syscall argument that is a out buffer (kernel should write to it) or if argument is in/out buffer or if there is an error in implementation. I'm not able to reproduce it (with iconv port compilation), could you tell me what exactly you're trying to compile? Or maybe you could send backtrace from make.core? +> I'm also not sure if that's correct behavior, some cerber output +> doesn't go to screen but instead on console (which is good in case of +> error where trace goes to logfiles, but bad in cases like displaying +> active cerber rules) That didn't happen in RC1. It will be fixed, I know about it. Rules shouldn't be listed via sysctl at all, it should be done via cbctl. +> I have feeling that RC2 is less stable than RC1, which IMO should be +> opposite. Don't worry. The only new big thing in cerb RC2 that could case problems is this protection against races in arguments. Many little bugs was removed after RC1, so IMHO we only have to stabilize race protector. --=20 Pawel Jakub Dawidek pa...@da... UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net |