Date: Thu, 13 Nov 2003 08:37:51 -0800 From: eculp@encontacto.net To: freebsd-current@freebsd.org Subject: Re: signal 12's everywhere on Current with update this morning. Message-ID: <20031113083751.byww8s4wc4cgkc8k@mail.encontacto.net> In-Reply-To: <3FB3A63B.6020303@despammed.com> References: <20031113064835.qccgccsoowkw0o00@mail.encontacto.net> <20031113145037.GR60410@submonkey.net> <20031113065514.kkcg0ckwsw88okcw@mail.encontacto.net> <3FB3A63B.6020303@despammed.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mensaje citado por Uwe Laverenz <laverenz@despammed.com>: | eculp@encontacto.net schrieb: | | > Thanks, I missed that. :( Sorry for the noise. | | You're not the only one who missed that. We killed 2 machines yesterday | evening (~11pm CET) this way. I think I did read UPDATING and I can't | remember any warning entries?! It's there now, of course so we were just | running cvsup a few hours too early I guess. ;) | | Anyway, things like this can happen if you decide to run -CURRENT. :-) Uwe, do you have any remote machines? I'm wondering what the correct sequence would be to update and reboot them. Thanks, ed -------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031113083751.byww8s4wc4cgkc8k>