From owner-freebsd-ports@FreeBSD.ORG Tue Jun 13 11:54:18 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21C5316A46F for ; Tue, 13 Jun 2006 11:54:18 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4153B43D66 for ; Tue, 13 Jun 2006 11:54:16 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail10.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k5DBsCP6024060 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Jun 2006 21:54:13 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k5DBsCCX001675; Tue, 13 Jun 2006 21:54:12 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k5DBsBdV001674; Tue, 13 Jun 2006 21:54:11 +1000 (EST) (envelope-from peter) Date: Tue, 13 Jun 2006 21:54:11 +1000 From: Peter Jeremy To: Andrew Pantyukhin Message-ID: <20060613115410.GA722@turion.vk2pj.dyndns.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: FreeBSD Ports , UMENO Takashi , Tobias Roth Subject: Re: xlockmore - serious security issue X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2006 11:54:18 -0000 On Tue, 2006-Jun-13 15:18:16 +0400, Andrew Pantyukhin wrote: >The problem is that xlockmore exits all by itself when >left alone for a couple of days. I've seen this as well. It looks like some of the modules (esp the 3D ones) are somewhat buggy. I invoke it from my time tracking tool so I just added a loop that re-invokes xlockmore unless it exited 0: /* The following loop ensures that xlock will restart if it dies * for any reason other than a password being entered. */ while (system("/usr/X11R6/bin/xlock +enablesaver +resetsaver" " -erasedelay 0") > 0) ; -- Peter Jeremy