There are two possible issues here. One is a packaging issue. If you package
Bacula to run as non-root, which can be done for both the Director and the
Storage daemon, then the packager must ensure that any new userid or group is
created when installing the package. For example, often the
Package: bacula-director-pgsql
Version: 1.38.11-5~bpo.1.0.1
Severity: normal
I tried to add bacula to ssl-cert so I could put its ssl key in
/etc/ssl/private. However, I got permission denied errors; checking
/proc/«pid»/status showed that Bacula did not initialize its
supplemental groups.
--
2 matches
Mail list logo
