From owner-freebsd-bugs@FreeBSD.ORG Mon Dec 15 04:50:41 2008 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2913F1065677 for ; Mon, 15 Dec 2008 04:50:41 +0000 (UTC) (envelope-from javanunes@gmail.com) Received: from mail-bw0-f14.google.com (mail-bw0-f14.google.com [209.85.218.14]) by mx1.freebsd.org (Postfix) with ESMTP id 7A67D8FC0C for ; Mon, 15 Dec 2008 04:50:40 +0000 (UTC) (envelope-from javanunes@gmail.com) Received: by bwz7 with SMTP id 7so5909786bwz.19 for ; Sun, 14 Dec 2008 20:50:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type; bh=QGtEij+T8pXH0Y5ga8suQR7IZnbseKarpgRkNAyQa/0=; b=udUFeUTnRkvlCZ8S0PL6+q9jYu6Ow/PQhNIRCoO/a4i7vOZORw8eil1sm9D/LYuO8I C6dgqaSFOML17HoD4uKBjYuSMuVzcC6n9ROT6+ppOxlU6sb+5dAPERu7l4LopCAshBTv T7+xmWPQeMZwm8KfMlBo3zuIm+++tzX1h+iSQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type; b=qvPQ3340Z75ql3AogZyvQqcuUWQy0mPQK38lvNsZUFsgi6lbTJCbolH9GtYPfho7if hmrmc2sXMxChWJ5RwxhTed0vn/n3N+Re8p1qLGV3kVlqqa8s8UwjeNzBj5JTpbIZWPYb 5LBUkg0oTGsZVACZvnC3WXx/p2knqMka40OMg= Received: by 10.223.111.19 with SMTP id q19mr6064087fap.58.1229316638662; Sun, 14 Dec 2008 20:50:38 -0800 (PST) Received: by 10.223.114.79 with HTTP; Sun, 14 Dec 2008 20:50:38 -0800 (PST) Message-ID: <425f5fc40812142050r5c3e72abm68aeebc535d89a48@mail.gmail.com> Date: Mon, 15 Dec 2008 02:50:38 -0200 From: "Java Nunes" To: dan-freebsd-bugs@ourbrains.org, freebsd-bugs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: RE: fork bomb no respects limits in freebsd 7.0 (semeador da discordia) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: javanunes@eminem.com List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 04:50:41 -0000 This error not exist in system no swap i see. To kill forkbomb problem i made a new class user in: /etc/login.conf so: amarrado:\ :memoryuse=20M:\ :maxproc=16:\ :memorylocked=18M:\ :cputime=6s:\ :vmemoryuse=19M:\ :filesize=2M:\ :datasize=2M:\ :stacksize=4M:\ :accounted:\ :path=/bin /usr/bin /usr/local/bin /usr/games/ /usr/local/sbin:\ :refreshtime=180d:\ :passwd_format=blf:\ :sessionlimit@:\ and put class cracker user like amarrado in vipw and cap_mkdb /etc/login.conf I have see the message in console when swap on : maxproc limit exceeded by uid 1010, please see tuning(7) and login.conf(5). maxproc limit exceeded by uid 1010, please see tuning(7) and login.conf(5). maxproc limit exceeded by uid 1010, please see tuning(7) and login.conf(5). maxproc limit exceeded by uid 1010, please see tuning(7) and login.conf(5). Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgpe rproc or the vm.pmap.pv_entry_max sysctl. But not anymore it shutdown my freebsd box >Java Nunes(javanunes@gmail.com)@2008.12.11 05:27:08 -0200: >> fBSD gives memory in spite of all limits. Is there any limit, which can stop >> adding memory for that forks ? >> limit it does not function in bsd? >Hmm, I understand there is a per process limit, that once exceeded kills >the process, I don't know if there is a system limit for max RAM. >_______________________________________________ >freebsd-bugs@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-bugs >To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" http://ceboliceta.blogspot.com