>>>>> On Thu, 29 Dec 2005 22:40:23 +0200, "Timo Neuvonen" <[EMAIL PROTECTED]> >>>>> said:
>> DIR as non-root: >> I suspect that the configuration files were not accessible by user >> bacula. You can easily check this using the ls command (like ls -l >> /etc/bacula ) and see if user bacula has read access to the necessary Timo> files. >> strace can help a lot when tracing that sort of problem. >> Perhaps there even isn't a bacula user or group on your system. >> Timo> All *conf files in /etc/bacula have rights 640, owner root, group bacula. Timo> So, they are readable by user bacula. I changed this already earlier today, Timo> when I expected this to be the problem after noticing that rpmnew-conf files Timo> had this group/rights setting. Anyway, it didn't help, didn't make director Timo> to start. OK, but there are other non *conf files that bacula-dir writes on startup. For instance there is a file used for console messages. The -f option might show that failing. __Martin ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
