>>>>> On Wed, 18 Jan 2006 16:09:57 +0100, Kern Sibbald <[EMAIL PROTECTED]> said:
Kern> On Wednesday 18 January 2006 15:30, Timo Neuvonen wrote: >> > If you do find a solution other than running as root, please be sure >> > to send it to the list as a number of users seem to be having the same >> > problem. >> >> So far, this seems to work: >> >> - director running as bacula / bacula >> - SD running as user bacula / group disk >> - bacula removed from group disk (to strip director's "disk" privileges) >> - /dev/nst0: root:disk 0660 Kern> Thanks for the feedback. Kern> Hmmm. It is probably better to run that way, but I still don't understand why Kern> the previous setup didn't work unless there was something wrong with the gid Kern> bacula or it didn't actually get added to the disk group. I think it is because the drop() function calls setgroups() with the selected gid, so even if the bacula user is a member of the disk group in /etc/group, the process is not in that group. At least I think that's what setgroups() does. The members listed in /etc/group only affect callers of the initgroups() function, such as login or su. __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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
