Complete path in crontab is it ok? #445

New Issue

Closed

opened 2021-09-03 20:37:35 +00:00 by jacobo · 3 comments

jacobo commented 2021-09-03 20:37:35 +00:00

Copy Link

Thanks to develop borgmatic!

What I'm trying to do and why

Run via cron borgmatic

Actual behavior (if a bug)

Cronjob with complete path works but only borgmatic doesn't work

Complete path. it works:

00 22 * * * /usr/local/bin/borgmatic

Only command does not work:

00 22 * * * borgmatic

Expected behavior (if a bug)

I am curious about why it. Can you explain it to me, please?

Other notes / implementation ideas

Environment

borgmatic 1.5.13

borgmatic installation method:

via pip

Borg version: [version here]

borg 1.1.9

Python version: [version here]

Python 3.7.3

operating system and version: [OS here]

Debian Buster

Thanks to develop borgmatic! #### What I'm trying to do and why Run via cron borgmatic #### Actual behavior (if a bug) Cronjob with complete path works but only borgmatic doesn't work Complete path. it works: ``` 00 22 * * * /usr/local/bin/borgmatic ``` Only command does not work: ``` 00 22 * * * borgmatic ``` #### Expected behavior (if a bug) I am curious about why it. Can you explain it to me, please? #### Other notes / implementation ideas #### Environment borgmatic 1.5.13 **borgmatic installation method:** via pip **Borg version:** [version here] borg 1.1.9 **Python version:** [version here] Python 3.7.3 **operating system and version:** [OS here] Debian Buster

witten added the

question / support

label 2021-09-03 21:56:47 +00:00

witten commented 2021-09-03 22:08:54 +00:00

Owner

Copy Link

Thanks for the question! What's going on here is that the borgmatic binary is installed in a location (/usr/local/bin/) that's not in your default PATH, the set of directories that are searched by default when you type a command. If you're running cron globally / system-wide, then it's running as the root user, and thus we're talking about the root user's PATH. Here are some instructions about modifying the PATH for borgmatic here: https://torsion.org/borgmatic/docs/how-to/set-up-backups/

And here is some general documentation about PATHs on Linux: https://www.computerhope.com/issues/ch001647.htm

Let me know if that helps!

Thanks for the question! What's going on here is that the borgmatic binary is installed in a location (`/usr/local/bin/`) that's not in your default `PATH`, the set of directories that are searched by default when you type a command. If you're running cron globally / system-wide, then it's running as the `root` user, and thus we're talking about the `root` user's `PATH`. Here are some instructions about modifying the `PATH` for borgmatic here: https://torsion.org/borgmatic/docs/how-to/set-up-backups/ And here is some general documentation about `PATH`s on Linux: https://www.computerhope.com/issues/ch001647.htm Let me know if that helps!

jacobo commented 2021-09-04 01:57:06 +00:00

Author

Copy Link

Your explanation was very useful. Thank you :)

Your explanation was very useful. Thank you :)

jacobo closed this issue 2021-09-04 01:57:06 +00:00

witten commented 2021-09-04 03:15:12 +00:00

Owner

Copy Link

Glad to hear it!

Glad to hear it!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#445

No description provided.