On Fri, Jun 11, 2021 at 04:09:35PM -0700, Gary L. Roach wrote: > I rebooted the system and then ran: > > * systemctl status backuppc.service** > **● backuppc.service - LSB: Launch backuppc server** > ** Loaded: loaded (/etc/init.d/backuppc; generated)**
Ouch! > ** Active: active (running) since Fri 2021-06-11 15:59:17 PDT; 6min ago** > ** Docs: man:systemd-sysv-generator(8)** > ** Process: 706 ExecStart=/etc/init.d/backuppc start (code=exited, > status=0/SUCCESS)** > ** Tasks: 2 (limit: 4915)** > ** Memory: 26.9M** > ** CGroup: /system.slice/backuppc.service** > ** ├─764 /usr/bin/perl /usr/share/backuppc/bin/BackupPC -d** > ** └─765 /usr/bin/perl > /usr/share/backuppc/bin/BackupPC_trashClean* > > BackupPC seems to have loaded and started on boot up. Does this help. Yes, this is a good starting point. This particular service is launched by a legacy sysv init.d script. In many cases, these scripts will read a file in /etc/default/ which contains additional configuration. Let's see if I can find a copy of this package on sources.debian.org .... Here: <https://sources.debian.org/src/backuppc/3.3.2-2+deb10u1/> And then: <https://sources.debian.org/src/backuppc/3.3.2-2+deb10u1/init.d/src/debian-backuppc/> If I'm reading this correctly, this script doesn't read any config files from /etc/default/. If that's true, then you'll need to edit the init.d script itself to change its configuration. So: go ahead and edit /etc/init.d/backuppc (ouch!) knowing that your changes may be lost and need to be re-done when the package gets updated. Put your PATH=... command right in the script. Set it to whatever you need it to be. The Debian maintainer of this package could have done a few things differently to make this a little easier for you, but... they didn't. So here you are.
