On 16 Aug 2007 at 18:10, Per olof Ljungmark wrote: > [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?
See http://bugs.bacula.org/view.php?id=923 -- Dan Langille - http://www.langille.org/ Available for hire: http://www.freebsddiary.org/dan_langille.php ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
