From owner-freebsd-ports@FreeBSD.ORG  Thu Aug 16 16:27:49 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5F11116A418
	for <ports@FreeBSD.org>; Thu, 16 Aug 2007 16:27:49 +0000 (UTC)
	(envelope-from peo@intersonic.se)
Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com
	[212.247.8.98])
	by mx1.freebsd.org (Postfix) with ESMTP id 2763D13C4D0
	for <ports@FreeBSD.org>; Thu, 16 Aug 2007 16:27:49 +0000 (UTC)
	(envelope-from peo@intersonic.se)
X-Virus-Scanned: amavisd-new at inter-sonic.com
Message-ID: <46C476F2.3050401@intersonic.se>
Date: Thu, 16 Aug 2007 18:10:26 +0200
From: Per olof Ljungmark <peo@intersonic.se>
Organization: Intersonic AB
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ports@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: bacula-users@lists.sourceforge.net
Subject: bacula 2.2.0 fails to start, pidfile
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2007 16:27:49 -0000

[crossposting out of impatience, sorry for that]

Hi,

I just upgraded our bacula-server from 1.3.8 to version 2.2.0 using 
portupgrade.

Now bacula-dir fails to start:
Could not open pid file. /var/run/bacula-dir.9101.pid ERR=Permission denied

I assume it tries to start as the "bacula" user, but /var/run is not 
writable. Common practice seems to be to create a writable subdirectory 
instead, as in /var/run/bacula.

Anyone has a fix for this? Maybe a configuration directive would do it?

Per olof

FreeBSD 6.2-STABLE #0: Tue Jun  5
bacula-server-2.2.0