From owner-freebsd-questions Wed Apr 4 8:49: 1 2001 Delivered-To: freebsd-questions@freebsd.org Received: from relay.ioffe.rssi.ru (relay.ioffe.rssi.ru [194.85.224.33]) by hub.freebsd.org (Postfix) with ESMTP id D727D37B71E for ; Wed, 4 Apr 2001 08:48:52 -0700 (PDT) (envelope-from kopts@astro.ioffe.rssi.ru) Received: from astro.ioffe.rssi.ru (astro.ioffe.rssi.ru [194.85.229.130]) by relay.ioffe.rssi.ru (8.9.1/8.9.1) with ESMTP id TAA18248 for ; Wed, 4 Apr 2001 19:48:41 +0400 (MSD) Received: by astro.ioffe.rssi.ru (8.9.3/Clnt-2.14-AS-eef) id TAA24759; Wed, 4 Apr 2001 19:48:36 +0400 (MSD) Date: Wed, 4 Apr 2001 19:48:36 +0400 (MSD) From: Alexey Koptsevich To: questions@freebsd.org Subject: xlock releases X too slow Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, We usually have several computational tasks running on our server, and when users xlock their X it sometimes gets too much time for it to release X (I have seen a warning about it in the manual), and if xlock runs with the high priority it allocates too much CPU time even in the blank mode (btw, why so?) Is there a workaround to make it allocate not much time and to release X in reasonable time? Please cc: me your reply. Thanks, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message