From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3530 invoked from network); 17 Apr 2007 09:01:04 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO autolearn=ham version=3.1.8 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 17 Apr 2007 09:01:04 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 84407 invoked from network); 17 Apr 2007 09:00:58 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 17 Apr 2007 09:00:58 -0000 Received: (qmail 7888 invoked by alias); 17 Apr 2007 09:00:54 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 23279 Received: (qmail 7878 invoked from network); 17 Apr 2007 09:00:53 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 17 Apr 2007 09:00:53 -0000 Received: (qmail 84129 invoked from network); 17 Apr 2007 09:00:53 -0000 Received: from cs1.cs.huji.ac.il (132.65.16.10) by a.mx.sunsite.dk with SMTP; 17 Apr 2007 09:00:50 -0000 Received: from wrath.cs.huji.ac.il ([132.65.80.62]) by cs1.cs.huji.ac.il with esmtp id 1HdjYQ-000K5l-8L for zsh-workers@sunsite.dk; Tue, 17 Apr 2007 12:00:50 +0300 Message-ID: <46248CC2.4010901@cs.huji.ac.il> Date: Tue, 17 Apr 2007 12:00:50 +0300 From: David Peer Reply-To: davidpeer@cs.huji.ac.il Organization: Hebrew University - Computer User-Agent: Icedove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: zsh-workers@sunsite.dk Subject: Bug in ulimit ? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, I'm using zsh 4.3.2-25 on debian, and noticed that when any user run: ulimit -t 0 from its shell, he manages to disable the cputime limitation if any. for example: I have a debian system that has cpu time limitation of 1 minute soft, and 2 minutes hard. If the user run: ulimit -t 0, he can run jobs without any cputime limitation: The soft limit: <2|0>dib@mafalda:~> limit | grep cputime cputime 1:00 The hard limit: <5|0>dib@mafalda:~> ulimit -t unlimited <6|0>dib@mafalda:~> limit | grep cputime cputime 2:00 So far so good. But: <7|0>dib@mafalda:~> ulimit -t 0 <8|0>dib@mafalda:~> limit | grep cputime cputime 0:00:00 Now the user can run processes without cpu time limitation. You can see the output from "top" command, that it ran the job "testload" for more then 6 minutes. 4754 dib 30 5 1556 336 276 R 97.0 0.1 6:16.52 testload Thanks in advanced, David Peer.