ip does not work / does not produce output when run with cron












0














I have a bash script in which I use the ip r command. When I run the script in bash it works but when cron runs it it does not.



This is the line in my script:



ping -q -w 1 -c 1 `ip r | grep -m 1 default | cut -d ' ' -f 3` >/dev/null || exit


To test that the ip r command is the problem I added notify-send "TEST $(ip r)" in front of that line. When I execute the script in bash it sends the notification with TEST and the output of ip r but when run with cron the notification only contains TEST.










share|improve this question






















  • @KamilMaciorowski whereis ip gives ip: /usr/sbin/ip /usr/share/man/man8/ip.8.gz. How do I find out what $PATH it is? Running echo $PATH in bash prints /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alex/.local/bin.
    – Alexander
    Dec 14 at 11:01










  • @KamilMaciorowski You were right, it was a problem with $PATH. I now added ` eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"` at the beginning of my crontab -e command and now the ip r works in cron as well.
    – Alexander
    Dec 14 at 11:08
















0














I have a bash script in which I use the ip r command. When I run the script in bash it works but when cron runs it it does not.



This is the line in my script:



ping -q -w 1 -c 1 `ip r | grep -m 1 default | cut -d ' ' -f 3` >/dev/null || exit


To test that the ip r command is the problem I added notify-send "TEST $(ip r)" in front of that line. When I execute the script in bash it sends the notification with TEST and the output of ip r but when run with cron the notification only contains TEST.










share|improve this question






















  • @KamilMaciorowski whereis ip gives ip: /usr/sbin/ip /usr/share/man/man8/ip.8.gz. How do I find out what $PATH it is? Running echo $PATH in bash prints /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alex/.local/bin.
    – Alexander
    Dec 14 at 11:01










  • @KamilMaciorowski You were right, it was a problem with $PATH. I now added ` eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"` at the beginning of my crontab -e command and now the ip r works in cron as well.
    – Alexander
    Dec 14 at 11:08














0












0








0







I have a bash script in which I use the ip r command. When I run the script in bash it works but when cron runs it it does not.



This is the line in my script:



ping -q -w 1 -c 1 `ip r | grep -m 1 default | cut -d ' ' -f 3` >/dev/null || exit


To test that the ip r command is the problem I added notify-send "TEST $(ip r)" in front of that line. When I execute the script in bash it sends the notification with TEST and the output of ip r but when run with cron the notification only contains TEST.










share|improve this question













I have a bash script in which I use the ip r command. When I run the script in bash it works but when cron runs it it does not.



This is the line in my script:



ping -q -w 1 -c 1 `ip r | grep -m 1 default | cut -d ' ' -f 3` >/dev/null || exit


To test that the ip r command is the problem I added notify-send "TEST $(ip r)" in front of that line. When I execute the script in bash it sends the notification with TEST and the output of ip r but when run with cron the notification only contains TEST.







linux bash cron






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 14 at 10:41









Alexander

1265




1265












  • @KamilMaciorowski whereis ip gives ip: /usr/sbin/ip /usr/share/man/man8/ip.8.gz. How do I find out what $PATH it is? Running echo $PATH in bash prints /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alex/.local/bin.
    – Alexander
    Dec 14 at 11:01










  • @KamilMaciorowski You were right, it was a problem with $PATH. I now added ` eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"` at the beginning of my crontab -e command and now the ip r works in cron as well.
    – Alexander
    Dec 14 at 11:08


















  • @KamilMaciorowski whereis ip gives ip: /usr/sbin/ip /usr/share/man/man8/ip.8.gz. How do I find out what $PATH it is? Running echo $PATH in bash prints /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alex/.local/bin.
    – Alexander
    Dec 14 at 11:01










  • @KamilMaciorowski You were right, it was a problem with $PATH. I now added ` eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"` at the beginning of my crontab -e command and now the ip r works in cron as well.
    – Alexander
    Dec 14 at 11:08
















@KamilMaciorowski whereis ip gives ip: /usr/sbin/ip /usr/share/man/man8/ip.8.gz. How do I find out what $PATH it is? Running echo $PATH in bash prints /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alex/.local/bin.
– Alexander
Dec 14 at 11:01




@KamilMaciorowski whereis ip gives ip: /usr/sbin/ip /usr/share/man/man8/ip.8.gz. How do I find out what $PATH it is? Running echo $PATH in bash prints /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alex/.local/bin.
– Alexander
Dec 14 at 11:01












@KamilMaciorowski You were right, it was a problem with $PATH. I now added ` eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"` at the beginning of my crontab -e command and now the ip r works in cron as well.
– Alexander
Dec 14 at 11:08




@KamilMaciorowski You were right, it was a problem with $PATH. I now added ` eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"` at the beginning of my crontab -e command and now the ip r works in cron as well.
– Alexander
Dec 14 at 11:08










1 Answer
1






active

oldest

votes


















0














The $PATH variable was not set when run with cron. So I ran echo $PATH in bash and then set the $PATH variable to that output in the crontab command.



For that I added



eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"


in crontab -e where everything after PATH= is the output of the command echo $PATH when run in bash.






share|improve this answer

















  • 3




    Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
    – Kamil Maciorowski
    Dec 14 at 11:31











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383544%2fip-does-not-work-does-not-produce-output-when-run-with-cron%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














The $PATH variable was not set when run with cron. So I ran echo $PATH in bash and then set the $PATH variable to that output in the crontab command.



For that I added



eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"


in crontab -e where everything after PATH= is the output of the command echo $PATH when run in bash.






share|improve this answer

















  • 3




    Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
    – Kamil Maciorowski
    Dec 14 at 11:31
















0














The $PATH variable was not set when run with cron. So I ran echo $PATH in bash and then set the $PATH variable to that output in the crontab command.



For that I added



eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"


in crontab -e where everything after PATH= is the output of the command echo $PATH when run in bash.






share|improve this answer

















  • 3




    Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
    – Kamil Maciorowski
    Dec 14 at 11:31














0












0








0






The $PATH variable was not set when run with cron. So I ran echo $PATH in bash and then set the $PATH variable to that output in the crontab command.



For that I added



eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"


in crontab -e where everything after PATH= is the output of the command echo $PATH when run in bash.






share|improve this answer












The $PATH variable was not set when run with cron. So I ran echo $PATH in bash and then set the $PATH variable to that output in the crontab command.



For that I added



eval "export PATH=/usr/local/bin:/usr/bin:/usr/local/sbin :/usr/sbin:/home/alex/.local/bin"


in crontab -e where everything after PATH= is the output of the command echo $PATH when run in bash.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 14 at 11:13









Alexander

1265




1265








  • 3




    Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
    – Kamil Maciorowski
    Dec 14 at 11:31














  • 3




    Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
    – Kamil Maciorowski
    Dec 14 at 11:31








3




3




Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
– Kamil Maciorowski
Dec 14 at 11:31




Cumbersome, I think. Please see this answer. A line starting with PATH= should do.
– Kamil Maciorowski
Dec 14 at 11:31


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383544%2fip-does-not-work-does-not-produce-output-when-run-with-cron%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Index of /

Tribalistas

Listed building