thx @alex & Nico,
I did something quite similar (for one particular user).
As I am pushing a .bashrc up to the target anyway at some point I added my PATH
in the same manner you suggets here via the edit Module.
> On 12/01/2021 1:26 PM Nico Kadel-Garcia wrote:
>
>
>
>
> On Monday, Novembe
On Monday, November 29, 2021 at 12:20:12 PM UTC-5 alex...@gmail.com wrote:
> Traverse /home and for each user:
> edit:
> ~/.bashrc
> with:
> export PATH="SOMETHING":$PATH"
>
>
This way lies madness, and a stack of security issues when someone or some
process sticks alternative binaries or sc
Traverse /home and for each user:
edit:
~/.bashrc
with:
export PATH="SOMETHING":$PATH"
On Monday, November 29, 2021 at 5:24:47 AM UTC-5 dick@geant.org wrote:
> Hi
>
> Your question seems to be around "installing barman" (no idea what that
> is), and while doing that you run into some gene
Hi
Your question seems to be around "installing barman" (no idea what that
is), and while doing that you run into some generic system administration
issue.
Ansible is not really relevant to both the issues. It's used to automate
things, but that implies that you already know how to do those things
I am trying my luck with installing barman as barman user (non-root) via ansible
At the end I need to adust the PATH of the barman user and have managed to add
the relevant location (/opt/barman/.local/bin) to the global PATH with the TASK
below (from a comment in
https://www.jeffgeerling.com/b
