Date: Sun, 22 Aug 2004 06:14:00 +1200 (NZST) From: Andrew McNaughton <andrew@scoop.co.nz> To: Simon <simon@optinet.com> Cc: FreeBSD-ISP List <freebsd-isp@freebsd.org> Subject: Re: reboot without forking Message-ID: <20040822053415.L1573@a2.scoop.co.nz> In-Reply-To: <20040821171337.79E8743D3F@mx1.FreeBSD.org> References: <20040821171337.79E8743D3F@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm currently not sure why I'm running into problems. I've been playing with resource limits, and may have solved the problem already - it only turns up every other month or so. Meanwhile I may be constraining the system more than it needs to be constrained. Being able to recover from a mistake seems like an important pre-requisite to loosening up constraints a bit. If there's any good documents out there on strategies for determining good resource limits, that would be helpful. Andrew McNaughton On Sat, 21 Aug 2004, Simon wrote: > Why are you running out of resources? have you considered enforcing limits > so the problem doesn't arise to begin with? > > -Simon > > On Sun, 22 Aug 2004 01:58:05 +1200 (NZST), Andrew McNaughton wrote: > >> >> Is there some sort of server I can run so that I can reboot a server in a >> situation where there are not available resources for forking? >> >> Best option I've got at present is to leave a ssh session running with a >> root shell. Seems I can get a reboot using `exec reboot` even when I >> can't fork. >> >> Andrew -- No added Sugar. Not tested on animals. May contain traces of Nuts. If irritation occurs, discontinue use. ------------------------------------------------------------------- Andrew McNaughton Living in a shack in Tasmania andrew@scoop.co.nz Between the bush and the sea Mobile: +61 422 753 792 http://staff.scoop.co.nz/andrew/cv.doc http://www.scoop.co.nz/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040822053415.L1573>