Red Hat Bugzilla – Bug 629914
Bacula daemons do not drop privileges
Last modified: 2010-11-11 08:36:57 EST
+++ This bug was initially created as a clone of Bug #629697 +++
Description of problem:
usually the bacula services (especially the director and the storage daemon) are not run as root. In the SPECfile's configure user and group are set to bacula (which is good). However, this only affects the upstream init scripts that aren'nt used in Fedora.
The Fedora scripts provide no way to make bacula-dir and bacula-sd drop privileges.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install a storage daemon or director
3. ps auxwww | grep bacula
bacula-dir and bacula-sd run as root
bacula-dir and bacula-sd should run as bacula
The fedora init scripts don't work as expected for bacula as they practically ignore /etc/sysconfig/bacula.
Please have a look at the upstream supplied initscripts that read /etc/sysconfig/bacula and support configuration of uid and gid through DIR_USER, DIR_GROUP, SD_USER, SD_GROUP, FD_USER and FD_GROUP and try to make yours at least a bit compatible to that.
It would probably also make sense to change the default group for bacula-sd from "bacula" to "disk" so writing to tapes works out of the box.
(writing to tapes currently works out of the box, because the SD does not drop privileges).
--- Additional comment from email@example.com on 2010-09-02 20:24:54 CEST ---
I just confirmed that this issue is also present in the RHEL 6 Beta as bacula-3.0.2-8.el6.src.rpm uses the same initscripts
*** This bug has been marked as a duplicate of bug 651786 ***