Date: Wed, 17 Mar 1999 16:25:58 -0700 (MST) From: wildcardus freakis <wildcard@dax.belen.k12.nm.us> To: freebsd-questions@FreeBSD.ORG Subject: Re: DOS in SWAP(er)? Message-ID: <Pine.BSF.3.96.990317162158.22370A-100000@dax.belen.k12.nm.us> In-Reply-To: <Pine.BSF.3.96.990317101053.16730A-100000@dax.belen.k12.nm.us>
next in thread | previous in thread | raw e-mail | index | archive | help
I was also able to recreate this behavior with lynx although it didn't re-prioritize -18 but like 36 ( which is wierd too cause I only thought the guage went to 20) so it didn't stick as long...but I was able to Zombify enough of them to get the out of memory error. On Wed, 17 Mar 1999, wildcardus freakis wrote: > Here is something wierd that I ran accross a couple of days ago... > > I have a 133 machine with 36M of swap space. > I am trying to run FBSD3.1-R > > I installed the latest version on `vim` from the ports collection...I > guess it by default compiles with X support...since I don't run X on this > machine it acts wierd. Anyway...here is the cool part... > > I accidently exec'd vim instead of vi, it started but no output was put to > my screen so I had to do a `kill -9` then a little while later I > accidently exec'd `vim` again and I get "error: out of swap space". > >From then on I get a login.core every time I tried to login...so I > rebooted, it did an fsck and started up...so I checked I started vim and > then killed it with -9 and it ate up 4M of swap every time I did it until > all the swap was used up. The swap never restored it self even when I let > it sit there for a good 2 hours. I wasn't even root, just a shmo user. > In my mind this seems very wrong, since any user can now DOS your system > just by starting 15 or 20 or 30 vim's and then doing a `killall vim` > > shouldn't swapper or something cleanup dirty processes? > > I have an output of top if anyone wants to see it but the gest of it is... > about 40 vims all sitting with a -18 priority and in a STOP state that > never disappear. > > could other improper binaries cause the same thing to happen? > > If anyone can verify this behavior let me know, I will post a script on > some Buglists, after informing FBSD of course. > > (I've been trying to get noticed in the bug comunity for some time. :) ) > > > _ASM_ > Sasha > > > > > > > > > > > > > > -----BEGIN GEEK CODE BLOCK----- > GCM/CS/CC/GO d--- s: a--- C+++(++++) ULB+++(++++) P+ L++(+++) E--- W+(++) N+ O > K---- W---- O M-- V PS! PE! Y++ PGP++(+++) t++:+++> 5++ X++@ R+@ tv++ b++:+++> DDI+++ D++ G++:+++> e:+> h*:++@ r- !y+ > -----END GEEK CODE BLOCK----- > www.geekcode.com > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: 2.6.2 > > mQCNAza/c7UAAAEEAOmJDB7LkJqynF6nlLRNTLPq23PKnU5G+mNCACKJBlzwJuQ8 > tohYSan+4QKY0l6Ton547LU/r49YNIx8tqACfLhbyMWiumOL1cRCYMufCnjEeWDa > d73LbKRvHgyMcGopiAIqLk7ieJ/Xc6joVN3GojpM3Zoy96dSUyTheUku+Y9tAAUR > tB93aWxkY2FyZEBpbi1kYXguYmVsZW4uazEyLm5tLnVz > =UM6D > -----END PGP PUBLIC KEY BLOCK----- > > This is the way the world ends > This is the way the world ends > This is the way the world ends > Not with a Bang, but with a whimper. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > 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?Pine.BSF.3.96.990317162158.22370A-100000>