As a followup to this message, I retraced my notes with regard to the
configuration options that I passed to ./configure and was reminded that I
had explicitly set the user and groups to the appropriate non-root user and
non-root group on my system:
--with-dir-user=admini
--with-dir-group=staff
--with-sd-user=admini
--with-sd-group=staff
--with-fd-user=admini
--with-fd-group=staff
I believe this has solved the problem (e.g., I still need to start the
bacula start script as the root user but then I noticed the PIDs were
running correctly with the user admini).
There has been other references in the documentation such that the file
daemon really needs to run as the root user so I'm wondering if I will get
myself into trouble having configured with the configure options for the
file daemon also specifying the non-root-user and non-root group?
Thank you.
On 9/9/07, Hydro Meteor <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've installed Bacula 2.2.1 on an Apple Intel Xserve running Mac OS X
> Server 10.4.10
>
> I am in the process of moving through the Tutorial (Chapter 9 in the
> User's Guide) -- I have not touched / edited / modify the default
> configuration files. This is a fresh install!
>
> I had hoped to be able to (per Chapter 9), run all of the Bacula daemons
> as a non-root user (on my system named admini). The non-root user (admini)
> has a different group (gid) than the root user, the group named "staff".
>
> When running the bacula script which starts all of the daemons, I'm
> receiving the following error regarding initgroups. I'm trying to track this
> down:
>
> admini$ ./bacula start
>
> Starting the Bacula Storage daemon
> > 09-Sep 19:44 xserve-sd: ERROR TERMINATION at bsys.c:698
> > Could not initgroups for group=staff, userid=admini: ERR=Operation not
> > permitted
> >
> > Starting the Bacula File daemon
> > 09-Sep 19:44 xserve-fd: ERROR TERMINATION at bsys.c:698
> > Could not initgroups for group=staff, userid=admini: ERR=Operation not
> > permitted
> >
> > Starting the Bacula Director daemon
> > 09-Sep 19:44 bacula-dir: ERROR TERMINATION at bsys.c:698
> > Could not initgroups for group=staff, userid=admini: ERR=Operation not
> > permitted
> >
>
> I'll continue to try and track this down to find out what I need to change
> on my systems such as privileges of Bacula configuration files and/or
> executable files and directories (so that a user with a primary group that
> is not the same as a root user's primary group) may run the daemons. Granted
> once I'm into production mode, the file daemon will indeed by run as the
> root user from what I've grokked of the Bacula documentation.
>
> In the mean time, if anyone has run into this problem before and has any
> suggestions, I'd be appreciative (I did a search on the mailing list
> archives for the past year on "initgroups" and virtually nothing showed up).
>
>
> Thank you,
>
> -H
>
>
>
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
