Date: Mon, 28 Apr 2003 17:39:51 -0400 From: "Shane Hale" <merlyn@dreaming.org> To: <freebsd-questions@freebsd.org> Subject: RE: Limiting Processes Message-ID: <02c201c30dce$b4af0960$0400a8c0@251AGerrardStE.dreamlabs.com> In-Reply-To: <20030428211115.GU22259@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02c201c30dce$b4af0960$0400a8c0>