[pkg-bacula-devel] fixuser-branch / /etc/defaults handling

[Sven Hartge]

On 29.08.2016 17:34, Carsten Leonhardt wrote:

>> But before we go anywhere with the fixuser-branch I want to ask some
>> things on bacula-devel concerning "-k" and "-u user -g group" and
>> capabilites.
> [...]
>> I want to ask Kern/bacula-devel if this is an acceptable approach or if
>> they see any problems with it.
> 
> Sure.
> 
> I've thought a bit more about the /etc/defaults/-defaults under
> /usr/share/... and am wondering how the users would notice that they
> need to update their local copy in /etc/defaults/ when the default in
> /usr/share/... changes. I'm sure I've seen a discussion about something
> like this before ...

It is a legitimate concern, yes. It also mainly is about systemd where
we need to preset some defaults. An init-script can contain code to do
so, systemd is not as flexible (by design).

But: if we go ahead and remove the option to chose the runtime-user then
the need for a defaults file for bacula-sd and bacula-dir vanishes, only
bacula-fd would need one to select nonroot-mode.

This would solve the problem of needing to inform the user of changed
defaults, because there are not defaults the user can (easily) change.

> IIRC OpenBSD warns in this case, but I don't think I've seen a mechanism
> for that in Debian. Where did you see this in Debian? My attempts on
> codesearch.debian.net didn't find an example.

https://codesearch.debian.net/search?q=EnvironmentFile%3D/usr&perpkg=1

icinga2. But, yes, not as many as I thought and I can't remember right
now where else I saw this.

Grüße,
Sven.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20160829/e5f7ace5/attachment.sig>