> To me it seems more like you have really problematic libc or kernel. Because > I see from your information that you have provided that you can get this > problem in quite a few situation.
> Are you sure that you do not have a broken installation like buggy kernel > or libc? dunno really.... this box has gone through a bit -- after last reinstall (to go from 32bit to amd64) it was etch all the way through (before etch was released). In general it functions ok (now uptime is 127 days) and it is a busy box (at least 5-10 people working at it at the same time). Kernel is 2.6.18-5-amd64 and unfortunately I can't reboot it at the moment (unless smth else brakes). libc6 is 2.3.6.ds1-13etch5 as of now... memory is ECC so no error goes undetected (it seems we are developing a problem with 1 dimm, but error was on Apr 21). If I am to reboot it, I will sure thing will bring somewhat newer kernel in. > I mean it should not really hang in fork... ;-) indeed... but everything is coded by humans, so... BTW -- xf4 VNC fork seems to be active, have you looked at it recently? I wonder if it might be worth switching to... http://xf4vnc.sourceforge.net/ > Best regards, > // Ola -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
