[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: $PATH problem



I rebooted the system and then ran:

 systemctl status backuppc.service
● backuppc.service - LSB: Launch backuppc server
   Loaded: loaded (/etc/init.d/backuppc; generated)
   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.


Gary R.

On 6/11/21 2:10 PM, Greg Wooledge wrote:
On Fri, Jun 11, 2021 at 01:48:47PM -0700, Gary L. Roach wrote:
I have been trying to install Backuppc on my system and have run into a
problem with the $PATH settings. I put the proper path setting in the
/etc/environment file which, on login, is supposed to supply that path to
all users. This worked fine for gary and root but not Backuppc user. The
path for backuppc doesn't have all of the paths needed.
Does this "backuppc" user actually log in?  Or does it simply start
services at boot time, or have cron jobs, or something else?

Files that configure your interactive environment at login (such as
/etc/environment) have no effect on cron jobs or systemd services or
other such things.

You'll need to identify what processes you'd like to alter, and how those
processes get started.  The procedure will be different for each kind of
startup.


Reply to: