From nobody@FreeBSD.org  Mon Jul 17 14:55:02 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1B08516A4DF
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 17 Jul 2006 14:55:02 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D200A43D45
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 17 Jul 2006 14:55:01 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k6HEt1fe017103
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 17 Jul 2006 14:55:01 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k6HEt1I0017102;
	Mon, 17 Jul 2006 14:55:01 GMT
	(envelope-from nobody)
Message-Id: <200607171455.k6HEt1I0017102@www.freebsd.org>
Date: Mon, 17 Jul 2006 14:55:01 GMT
From: kost <kost@ropnet.ru>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Possible wrong setrlimit() handling
X-Send-Pr-Version: www-2.3

>Number:         100439
>Category:       kern
>Synopsis:       [libc] Possible wrong setrlimit(2) handling (regression)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 17 15:00:31 GMT 2006
>Closed-Date:    Mon Sep 18 14:13:32 GMT 2006
>Last-Modified:  Mon Sep 18 14:13:32 GMT 2006
>Originator:     kost
>Release:        FreeBSD 6.1-RELEASE-p2
>Organization:
RopNet
>Environment:
FreeBSD www4.ropnet.ru 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #1: Mon Jun 26 23:56:29 MSD 2006     mar@www4.ropnet.ru:/usr/obj/usr/src/sys/WWW4  i386
>Description:
I've got a wrapper written in C.
It sets some limits on other scripts, which started in this wrapper.

Program makes syscall setrlimit() with RLIMIT_CPU, RLIMIT_NPROC limitations
and than starts some perl script like this:

  #!/usr/bin/perl
  while(1){;}

This program eats CPU and dies after few seconds depending on RLIMIT_CPU
parameter. There is no problem - everything correct.  But there is no string
in log files about process killing. I expect the following string in logs:

  pid 32429 (perl5.8.7), uid 0, was killed: exceeded maximum CPU limit

but it's empty.

Talking about RLIMIT_NPROC limit - everything Ok.
I've tested this script on old 5.2.1-RELEASE FreeBSD... there was no
questions... everything Ok too.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-i386->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sat Jul 29 07:51:04 UTC 2006 
Responsible-Changed-Why:  
This does not sound i386-specific. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=100439 

From: Maxim Konovalov <maxim@macomnet.ru>
To: kost <kost@ropnet.ru>
Cc: bugs-followup@freebsd.org
Subject: kern/100439
Date: Sat, 29 Jul 2006 23:12:34 +0400 (MSD)

 Hello,
 
 Just checked on 6.1-REL and HEAD:
 
 $ limits -t 2 /bin/sh -c 'while :; do :; done'
 killed
 $  dmesg -a | grep killed | tail -2
 pid 58356 (sh), uid 1001, was killed: exceeded maximum CPU limit
 Jul 29 23:09:57 shy kernel: pid 58356 (sh), uid 1001, was killed:
 exceeded maximum CPU limit
 $ uname -r
 6.1-RELEASE
 
 Are you sure everything is OK with logging?
 
 -- 
 Maxim Konovalov
State-Changed-From-To: open->closed 
State-Changed-By: maxim 
State-Changed-When: Mon Sep 18 14:13:13 UTC 2006 
State-Changed-Why:  
Feedback timeout. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=100439 
>Unformatted:
