Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #236003 > unrolled thread

$PATH problem

Back to article view | Back to linux.debian.user

Contents

  $PATH problem "Gary L. Roach" <garyroach719@gmail.com> - 2021-06-11 22:50 +0200
    Re: $PATH problem Greg Wooledge <greg@wooledge.org> - 2021-06-11 23:20 +0200
      Re: $PATH problem "Gary L. Roach" <garyroach719@gmail.com> - 2021-06-12 01:20 +0200
        Re: $PATH problem Bob Weber <bobrweber@gmail.com> - 2021-06-12 02:00 +0200
        Re: $PATH problem Greg Wooledge <greg@wooledge.org> - 2021-06-12 04:00 +0200
    Re: $PATH problem Bob Weber <bobrweber@gmail.com> - 2021-06-11 23:50 +0200

#236003 — $PATH problem

Hi all,

Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-16-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM

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.

Any suggestions?


Gary R.

[toc] | [next] | [standalone]

#236005

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.

[toc] | [prev] | [next] | [standalone]

#236011

[Multipart message — attachments visible in raw view] — view raw

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.
>

[toc] | [prev] | [next] | [standalone]

#236012

[Multipart message — attachments visible in raw view] — view raw

On 6/11/21 19:09, Gary L. Roach wrote:
> *systemctl status backuppc.service**
> *

Thats good.  Does the web interface work? Try:

http://ip-of-server/backuppc/index.cgi?action=summary

You might have to login.  Check the file /etc/backuppc/htpasswd. On my system it 
has the user and encrypted password for the bcckuppc user.  If you dont know the 
password then as root run "passwd backuppc".  That will allow you to change the 
backuppc user password.

-- 


*...Bob*

[toc] | [prev] | [next] | [standalone]

#236014

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.

[toc] | [prev] | [next] | [standalone]

#236006

[Multipart message — attachments visible in raw view] — view raw

On 6/11/21 16:48, Gary L. Roach wrote:
> Hi all,
>
> Operating System: Debian GNU/Linux 10
> KDE Plasma Version: 5.14.5
> Qt Version: 5.11.3
> KDE Frameworks Version: 5.54.0
> Kernel Version: 4.19.0-16-amd64
> OS Type: 64-bit
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 15.6 GiB of RAM
>
> 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.
>
> Any suggestions?
>
>
> Gary R.
>
My backuppc server has no /etc/environment file.  All the commands needed by 
backuppc are in its config with full paths to each command.  There is a MyPath 
setting in the Server Main Configuration Editor settings under Server but the 
doc says its only for keeping perl happy.  You get to this under the web 
interface for backuppc.

The Debian install should have fixed all the settings for you so that the server 
part just works.  You just have to add machines and and tell backuppc what to 
backup on each machine.

Does the backuppc service run?  You can see if there are any startup problems with

"journalctl -b -ru backuppc"

Each host has a log file and under the Server section there is a log file for 
backuppc itself.

The backuppc data is stored under /var/lib/backuppc (on my system that is s 
symbolic link to the actual disk/partition large enough to store all the backed 
up data, backuppc configs, log files and ssh keys).


-- 


*...Bob*

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web