From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25363 invoked by uid 1002); 7 Nov 2003 23:29:33 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 11492 invoked from network); 7 Nov 2003 23:29:32 -0000 From: Steven Elling To: gentoo-dev@gentoo.org Date: Fri, 7 Nov 2003 17:29:25 -0600 User-Agent: KMail/1.5.4 References: <3FA5AF6F.5030501@codewordt.co.uk> <200311041706.38185.ellings@kcnet.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311071729.25842.ellings@kcnet.com> Subject: Re: [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email) X-Archives-Salt: 282fcf4f-d104-45cd-b9ef-a3e0da6fa35f X-Archives-Hash: 3bf5b27241bf266e7c8e6e94e11709f1 On Tuesday 04 November 2003 19:00, Terje Kvernes wrote: > > first, slocate I/O shouldn't be able to bring your box to a crawl. > secondly, you're free to kill the processes while they're running. Well, slocate does bring my system to a crawl. More than likely due to the crappy/old hardware Gentoo is on. If I have to get something done I usually did kill the processes but as of late I just moved the cron jobs to weekly. > inject an ebuild with a version number high enough that you won't > ever see it again. I really don't want to resort to this because security flaws could exist in slocate that I may not be made aware of. -- gentoo-dev@gentoo.org mailing list