Date: Tue, 28 Oct 2014 15:12:53 -0500 From: Adam Vande More <amvandemore@gmail.com> To: "Reed A. Cartwright" <cartwright@asu.edu> Cc: RW <rwmaillists@googlemail.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: out of swap space Message-ID: <CA%2BtpaK3QJqMxEL%2BuL7pj4eUcCh6Zf-wsgJMNSovzAOgX=YU%2B8w@mail.gmail.com> In-Reply-To: <CALOkxux4BiF5J72ywE4ifpKpPg1kd%2BchQnQVB%2Btuk1p5X=9dgg@mail.gmail.com> References: <0fdf2022075b7a33f0abde4edd7c12a1@paz.bz> <CA%2BtpaK20Pt0A-G7KzJPhqXn%2BRruk8hF4B4nyhc0uKwxuHvfaMQ@mail.gmail.com> <20141028130146.6d2b6179@gumby.homeunix.com> <CALOkxux4BiF5J72ywE4ifpKpPg1kd%2BchQnQVB%2Btuk1p5X=9dgg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 28, 2014 at 2:08 PM, Reed A. Cartwright <cartwright@asu.edu> wrote: > We've run out of swap on a system with 512GB of memory and 1TB of swap > space. > > Processes get killed, including services. It is usually easiest to > reboot to start from a fresh system. > > The funny effect is that you can log in to SSH and get a shell, but > cannot run any binary that is not already cached in memory. That > confused the hell out of me until I checked memory and swap usage. You can use protect(1) to ensure the wrong things don't get killed. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK3QJqMxEL%2BuL7pj4eUcCh6Zf-wsgJMNSovzAOgX=YU%2B8w>