On Mon, Aug 14, 2017 at 5:55 PM, Michał Górny <[email protected]> wrote: > On pon, 2017-08-14 at 21:58 +0200, Thomas Beierlein wrote: >> >> * 'bacula-clientonly' becomes 'clientonly' > > This is still negative logic in disguise. clientonly = noserver. > >> * 'bacula-nodir' will be replaced by 'director' but with inverted logic >> * 'bacula-nosd' will be replaced by 'storage-daemon' (also inverted). >> >> 'director' and 'storage-daemon' will be active by default resulting in an >> installation with backup director and storage daemon enabled. >>
++ I guess to make it a bit more explicit, would it make sense to have 3 flags: client - install the client (or consider calling it file-daemon instead) director - install the director storage-daemon - install the storage daemon Omit the first if we always want the client. I don't see the need for a "clientonly" flag if each of the two server components already have their own flags. If somebody doesn't want to have to know what each of the components do they probably shouldn't be messing around with Bacula as it is anything but install-and-forget. -- Rich
