Julien Cigar wrote:
[...]
You should either change the permission on /dev/nst0 (dirty) or add the
bacula daemon to the correct group (look at /dev/nst0).
I think that will only work in the case where the storage daemon is run
setgid to that group; just adding the daemon's user to the group with
permission to access the drive is not sufficient.
I had a similar problem when I first installed bacula (only yesterday!).
I added the user 'bacula' to the 'tape' group, and set the permissions
on /dev/nst0 to
crw-rw---- 1 root tape 9, 128 Feb 26 2005 /dev/nst0
but the bacula storage daemon (running with -u bacula -g bacula) was
unable to access it. In the end, I figured out that bacula doesn't take
on the supplementary groups of the user it's running as.
(I ended up replacing the setgroups(2) call in lib/bsys.c with one to
initgroups(3) -- perhaps I should suggest this on bacula-devel?)
Stephen
--
Stephen Lewis
-------------------------------------------------------
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
