Op 03-05-11 16:05, Josh Fisher schreef: > On 5/3/2011 5:55 AM, Koenraad Lelong wrote: >> ... > > So, bacula:bacula cannot write, but bacula:disk can, yet all accessed > directories appear to be owned by bacula:bacula? What group does the > bacula-sd daemon run as? On Fedora, it is typical for bacula-dir to run > as bacula:bacula, while bacula-sd runs as bacula:disk. Perhaps this is > an selinux thing? Maybe the simple solution is to change everything to > be owned by bacula:disk and run bacula-sd as bacula:disk. > Hi,
I got a step further. Since I didn't know which user/group bacula was running as, pa aux showed only bacula-binaries running as root. So I tried to force the group to disk in the startup-script. I didn't see any difference, I forced the user in the startup-script. Then I saw bacula-sd running as bacula. Then I tried "barcode labels" in bconsole, this time with success. I'm using OpenSuse 11.4 to do my tests. Since there is no "official" package of bacula I had to download a contributed package. After installing the package I saw a file where it seemed bacula-sd was compiled with user and group bacula/bacula. So this is not the case I think. My only problem now I that I can't eject the disk with the button (after the autofs timeout). Something is using the disk, and I can't find what. lsof didn't show anything was using the disk. "eject /dev/sdb1" did eject the disk though. Now I have to study again to see how to use the setup. Thanks for your help. Regards, Koenraad. ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
