Date: Mon, 11 Jan 1999 09:26:44 +1000 From: Ken Allan <ken@freebsdrocks.com> To: questions@FreeBSD.ORG Subject: Remote Administration of Webservers Message-ID: <19990111092644.C7461@agamemnon.imgmkt.com>
next in thread | raw e-mail | index | archive | help
I guess we kind of have a problem. We have to remotely administer group of computers, and sometimes the computers go down, and don't come back up. Is there anything that we can do to make the rebooting process more robust? For example: Is there a modification that we can make to the boot manager to make it automatically default back to the kernel.old, and then the kernel.generic after a failed startup? Is there a way that we can get around a fsck error aborting the boot process to multiuser mode? Is there a way to hook up a console box or something the the freebsd box, so that if we recompile the kernel, and it fails to reboot, we can change kernels, or if there's a fsck error, that we can run fsck, and fix it up - even though the network hasn't yet started? Has anyone done, or had experience with solving problems as above? Any solutions? Thanks, Ken. -- Ken Allan ---------- No man is an island, but some of us are long peninsulas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990111092644.C7461>