On Sat, Nov 11, 2006 at 08:13:22PM +0100, Gergely CZUCZY wrote: > On Sat, Nov 11, 2006 at 02:02:46PM -0500, Kris Kennaway wrote: > > On Sat, Nov 11, 2006 at 07:57:47PM +0100, Gergely CZUCZY wrote: > > > > > > OK, seems weird to go through all the disruption of changing to a new > > > > OS instead of a few minutes work at a console to give us what we need > > > > to resolve the matter -- but whatever works for you. > > > already done some stuff like these movings... i'm familiars with them. > > > it's not about a few minutes work. it's about the few hours' downtime :) > > > > It's a few minutes to perform the additional work at the serial > > console when your system hangs, which is *required* for a developer to > > help with your problem. If you're not willing to do this, there's not > > much more we can do for you. > i will see what can i do. a serial console may be accessable, but i'm not > sure. > i will have to visit the server hotel and talk with the techies there. we > have two boxes there, and it may be somehow possible to connect their > serial ports. the problem is, they are far away in the room from each other. > the hotel only gives system console(VGA+ps2 keyboard) access if i ask. but > this bloody box sometimes ain't even responses to that anyways, the LCD > remains blank.
You can't even break to the debugger? > i'd like to solve this, but the technical opportunities are limited here. > we cannot have downtime, and if we have it have to be minimized. as you see > clients won't accept a reasons like "sorry, we were debugging this OS we > run at the server". > > the question will be that, when i have a serial link, and shit happens(tm), > should i inspect it myself, or should i scream somewhere for a more decent > person (maybe a developer) to check it? Did you read the developers handbook chapter I pointed you to, yet? > > After 6.2 is release will of course be too late for you, again. If > > the problem is not fixed by magic then you'll be in the same position > > you are now. > why too late? it usually go for a month with a reboot. and it should be > released in a month. as i see, it fits into the time :) Because (if it is a FreeBSD bug) then you'll have more work to do to apply a patch to your system, and also it won't help anyone else who might also be seeing the problem, until 6.3-RELEASE in ~6 months. Kris
pgpkzvMqvsL66.pgp
Description: PGP signature
