From owner-freebsd-questions@FreeBSD.ORG Mon Apr 28 14:40:31 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54A5D37B401 for ; Mon, 28 Apr 2003 14:40:31 -0700 (PDT) Received: from castle.dreaming.org (monalisa.creativehouse.com [209.82.34.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B52C43F3F for ; Mon, 28 Apr 2003 14:40:30 -0700 (PDT) (envelope-from merlyn@dreaming.org) Received: from localhost (localhost [127.0.0.1]) by castle.dreaming.org (Postfix) with ESMTP id AFA5F9F675 for ; Mon, 28 Apr 2003 17:40:26 -0400 (EDT) Received: from shadowfax (CPE0040f404e422-CM014400120707.cpe.net.cable.rogers.com [65.49.85.110]) by castle.dreaming.org (Postfix) with ESMTP id 50A079F65F for ; Mon, 28 Apr 2003 17:40:20 -0400 (EDT) From: "Shane Hale" To: Date: Mon, 28 Apr 2003 17:39:51 -0400 Message-ID: <02c201c30dce$b4af0960$0400a8c0@251AGerrardStE.dreamlabs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20030428211115.GU22259@dan.emsphone.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by AMaViS snapshot-20020300 Subject: RE: Limiting Processes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 21:40:31 -0000 It's not so much a load issue. I don't want these users constantly connected, as they treat it like a bot service, which we are far from. We have edited the login.conf but to no luck. Shan=0E -----Original Message----- From: Dan Nelson [mailto:dnelson@allantgroup.com]=20 Sent: Monday, April 28, 2003 5:11 PM To: Shane Hale Cc: freebsd-questions@freebsd.org Subject: Re: Limiting Processes In the last episode (Apr 28), Shane Hale said: > I'm trying to limit the amount of time a process will run in userland. > Some of the users on my the network decide to keep BitchX and IRC=20 > processes running for eons and I'm wondering if there is a way to stop > this. You can set per-process cpu limits in /etc/login.conf (the cputime capability). Although you may be misreading the CPU column. It's in minutes:seconds.fractions, so for example =20 > beastah 29501 0.0 1.2 3324 1460 p3 Ss+ 11Apr03 2:37.11 BitchX -n BeAsTaH irc.gamesnet.net (BitchX-1.0c19) This user started a session on the 11th, and it has consumed 2 minutes of CPU time. Not all that much for 17 days of real time. If you have a CPU load issue it's probably someplace else. If you just want to kill long-running processes on principle, the idled utility in ports/sysutils/idled might have a way to do that. --=20 Dan Nelson dnelson@allantgroup.com