From owner-freebsd-questions@FreeBSD.ORG Sat Jun 27 15:29:34 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC13E106564A for ; Sat, 27 Jun 2009 15:29:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 879DD8FC12 for ; Sat, 27 Jun 2009 15:29:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-195-8-131.dynamic.qsc.de [92.195.8.131]) by mx02.qsc.de (Postfix) with ESMTP id DC8C516C0035; Sat, 27 Jun 2009 17:29:32 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n5RFTQYm005940; Sat, 27 Jun 2009 17:29:26 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 27 Jun 2009 17:29:25 +0200 From: Polytropon To: Charles Howse Message-Id: <20090627172925.cfc9609e.freebsd@edvax.de> In-Reply-To: References: Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: Stale lock files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2009 15:29:35 -0000 On Sat, 27 Jun 2009 10:00:24 -0500, Charles Howse wrote: > What are stale lock files? > I've been having them for a few weeks now, they need to go away! Lock files are used by several programs to indicate file-wise that they are running. The lock file is created when the program starts, and usually deleted when it ends. If it is interrupted (due to an error or ^C), the lock file isn't removed. Most programs remove stale lock files by theirselves when they are started again (e. g. fetchmail). It's possible that there are programs that refuse to start, because the lock file (falsely) indicates that the program is already running. The location of the lock file seems to depend on the respective program. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...