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 majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message