Date: Wed, 18 Aug 1999 01:24:53 +0600 (ESS) From: Ilia Chipitsine <ilia@cgilh.chel.su> To: Alec Kalinin <alec@relex.ru> Cc: Mark Newton <newton@internode.com.au>, Oleg Derevenetz <oleg@oleg.sani-c.vrn.ru>, freebsd-hackers@FreeBSD.ORG Subject: Re: Probably bug with allocation memory in FreeBSD-3.2-RELEASE Message-ID: <Pine.BSF.4.05.9908180123410.268-100000@localhost.cgu.chel.su> In-Reply-To: <027401bee88f$2e503b90$a34562c3@alec.relex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Aug 1999, Alec Kalinin wrote: > > > Why i think this is bug? Because any user can hung FreeBSD, settings in > > > /etc/login.conf can't help. > > >Are you sure about that? Setting datasize limits will prevent > >malloc() from doing what you're trying to make it do. Are you > >sure you're setting your login.conf settings properly? > guys, just a silly question ! how dod you think login.conf works with xdm ?! right ! xdm simply ignores it ... > > I am sure, that setting limits in "/etc/login.conf" is not good decision. I > try to explain. > > First of all, if i set limits more than swap space, one user can hung > system. But, if i set limit equal half swap space, two different users can > hung system. > > Than, i don't set limits for root process. And combinantion "squid + > Netscape with java applet" from root may hung system. > > While 3.2-system can't simply kill this process like 2.2.8-system? I think, > killing this process -- best solution. > > Good luck, > Alec. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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.4.05.9908180123410.268-100000>