I don't understand what the benefit is of running a local service using a
network account. The machine should also allow login by admins and grant sudo
privileges according to network auth, but local services are generally run with
local accounts to maximize resiliency. This is especially important for a
backup server as its primary benefit is to let you recover information when
something about your machines is NOT running properly.
Creating an unnecessary dependency for a backup server to backup or restore
would run counter to my DR/CoOp design methodology. That said, my server is
integrated into FreeIPA and users log in with their network credentials to view
their own backups. Is this the desired outcome?
ED.
> On 2019, Dec 5, at 12:59 AM, Kenneth Porter <sh...@sewingwitch.com> wrote:
>
> On 12/4/2019 7:07 AM, G.W. Haywood via BackupPC-users wrote:
>>
>> Why does this scenario give me a churning feeling in my stomach?
>
> Why should it? Centralized management of credentials is a reasonable thing to
> do.
>
> My suspicion is that the BackupPC service is trying to start before the
> credentials server is up. This is where you need systemd, to make sure the
> order of startup is obeyed, and to allow dynamic conditions such as a
> slow-starting credentials server. The default systemd unit file for BackupPC
> doesn't check for this. You need to extend it to add a dependency on
> connectivity to the credentials server.
>
>
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
