Bashrc, shell script and crontab












0















I'm trying to use the functions defined in /home/my_username/.bashrc in a shell script that gets executed by crontab. 



#crontab -l



# m h  dom mon dow   command

  * *  * * * /bin/sh /home/my_username/CronTab_shell_script.sh >> /home/my_username/Desktop/file.log


Let's say I have the mounted() function saved in 



/home/my_username/.bashrc 



function mounted(){



    if mount|grep $1; then

    echo "mounted"

    else

    echo "not mounted"

    fi



 }


How can I call and use the mounted() function from the 



/home/my_username/CronTab_shell_script.sh





bash scripts cron bashrc







share|improve this question




















  • 1





    The easiest way is to put this function into the body of CronTab_shell_script.sh :)

    – pa4080
    Sep 13 '17 at 12:09
















0















I'm trying to use the functions defined in /home/my_username/.bashrc in a shell script that gets executed by crontab. 



#crontab -l



# m h  dom mon dow   command

  * *  * * * /bin/sh /home/my_username/CronTab_shell_script.sh >> /home/my_username/Desktop/file.log


Let's say I have the mounted() function saved in 



/home/my_username/.bashrc 



function mounted(){



    if mount|grep $1; then

    echo "mounted"

    else

    echo "not mounted"

    fi



 }


How can I call and use the mounted() function from the 



/home/my_username/CronTab_shell_script.sh





bash scripts cron bashrc







share|improve this question




















  • 1





    The easiest way is to put this function into the body of CronTab_shell_script.sh :)

    – pa4080
    Sep 13 '17 at 12:09














0












0








0








I'm trying to use the functions defined in /home/my_username/.bashrc in a shell script that gets executed by crontab. 



#crontab -l



# m h  dom mon dow   command

  * *  * * * /bin/sh /home/my_username/CronTab_shell_script.sh >> /home/my_username/Desktop/file.log


Let's say I have the mounted() function saved in 



/home/my_username/.bashrc 



function mounted(){



    if mount|grep $1; then

    echo "mounted"

    else

    echo "not mounted"

    fi



 }


How can I call and use the mounted() function from the 



/home/my_username/CronTab_shell_script.sh





bash scripts cron bashrc







share|improve this question
















I'm trying to use the functions defined in /home/my_username/.bashrc in a shell script that gets executed by crontab. 



#crontab -l



# m h  dom mon dow   command

  * *  * * * /bin/sh /home/my_username/CronTab_shell_script.sh >> /home/my_username/Desktop/file.log


Let's say I have the mounted() function saved in 



/home/my_username/.bashrc 



function mounted(){



    if mount|grep $1; then

    echo "mounted"

    else

    echo "not mounted"

    fi



 }


How can I call and use the mounted() function from the 



/home/my_username/CronTab_shell_script.sh





bash scripts cron bashrc




bash scripts cron bashrc






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 13 '17 at 11:43









Yaron

9,22171941




9,22171941










asked Sep 13 '17 at 11:41









IDKIDK

188213




188213








  • 1





    The easiest way is to put this function into the body of CronTab_shell_script.sh :)

    – pa4080
    Sep 13 '17 at 12:09














  • 1





    The easiest way is to put this function into the body of CronTab_shell_script.sh :)

    – pa4080
    Sep 13 '17 at 12:09








1




1





The easiest way is to put this function into the body of CronTab_shell_script.sh :)

– pa4080
Sep 13 '17 at 12:09





The easiest way is to put this function into the body of CronTab_shell_script.sh :)

– pa4080
Sep 13 '17 at 12:09










2 Answers
2






active

oldest

votes


















2














Cron runs with a limited shell and won't have access to your regular environment.



You could put source /home/my_username/.bashrc at the beginning of /home/my_username/CronTab_shell_script.sh to make the function available.



You could also source your .bashrc in your crontab:



#crontab -l



# m h  dom mon dow   command

  * *  * * * . /home/my_username/.bashrc; /bin/sh /home/my_username/CronTab_shell_script.sh >> home/my_username/Desktop/file.log





share|improve this answer



















  • 1





    +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

    – pa4080
    Sep 13 '17 at 12:15



















2














1. Run the correct shell



* *  * * * /bin/sh .....


You are not running bash, you are running sh, so you should not expect .bashrc to be loaded!



Try this instead:



* *  * * * /bin/bash .....


2. Work around Ubuntu's default .bashrc



Another problem might be that Ubuntu's default .bashrc script starts with this guard:



# If not running interactively, don't do anything

case $- in

    *i*) ;;

      *) return;;

esac


Any lines you add below this will not be loaded by your cron script because cronjobs do not run in an interactive environment.



The solution: Put functions for scripts above this guard. Keep setup for the user below this guard.



3. Load the complete user login environment



On some systems I find its easiest to use --login to ensure the shell has the same things loaded that I have at the command line.



* *  * * * bash --login /path/to/script.sh



* *  * * * bash --login -c "your command here"





share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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%2faskubuntu.com%2fquestions%2f955415%2fbashrc-shell-script-and-crontab%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    Cron runs with a limited shell and won't have access to your regular environment.



    You could put source /home/my_username/.bashrc at the beginning of /home/my_username/CronTab_shell_script.sh to make the function available.



    You could also source your .bashrc in your crontab:



    #crontab -l
    

    
# m h  dom mon dow   command
    
  * *  * * * . /home/my_username/.bashrc; /bin/sh /home/my_username/CronTab_shell_script.sh >> home/my_username/Desktop/file.log





    share|improve this answer



















    • 1





      +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

      – pa4080
      Sep 13 '17 at 12:15
















    2














    Cron runs with a limited shell and won't have access to your regular environment.



    You could put source /home/my_username/.bashrc at the beginning of /home/my_username/CronTab_shell_script.sh to make the function available.



    You could also source your .bashrc in your crontab:



    #crontab -l
    

    
# m h  dom mon dow   command
    
  * *  * * * . /home/my_username/.bashrc; /bin/sh /home/my_username/CronTab_shell_script.sh >> home/my_username/Desktop/file.log





    share|improve this answer



















    • 1





      +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

      – pa4080
      Sep 13 '17 at 12:15














    2












    2








    2







    Cron runs with a limited shell and won't have access to your regular environment.



    You could put source /home/my_username/.bashrc at the beginning of /home/my_username/CronTab_shell_script.sh to make the function available.



    You could also source your .bashrc in your crontab:



    #crontab -l
    

    
# m h  dom mon dow   command
    
  * *  * * * . /home/my_username/.bashrc; /bin/sh /home/my_username/CronTab_shell_script.sh >> home/my_username/Desktop/file.log





    share|improve this answer













    Cron runs with a limited shell and won't have access to your regular environment.



    You could put source /home/my_username/.bashrc at the beginning of /home/my_username/CronTab_shell_script.sh to make the function available.



    You could also source your .bashrc in your crontab:



    #crontab -l
    

    
# m h  dom mon dow   command
    
  * *  * * * . /home/my_username/.bashrc; /bin/sh /home/my_username/CronTab_shell_script.sh >> home/my_username/Desktop/file.log






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Sep 13 '17 at 11:55









    GfeiGfei

    212




    212








    • 1





      +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

      – pa4080
      Sep 13 '17 at 12:15














    • 1





      +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

      – pa4080
      Sep 13 '17 at 12:15








    1




    1





    +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

    – pa4080
    Sep 13 '17 at 12:15





    +1, but I think the Shell must be bash, it should be declared into the beginning of the script as #!/bin/bash and /bin/sh should be removed from the cron job. Also, maybe, the function should be exported after its definition in .bashrc : export -f mounted.

    – pa4080
    Sep 13 '17 at 12:15













    2














    1. Run the correct shell



    * *  * * * /bin/sh .....


    You are not running bash, you are running sh, so you should not expect .bashrc to be loaded!



    Try this instead:



    * *  * * * /bin/bash .....


    2. Work around Ubuntu's default .bashrc



    Another problem might be that Ubuntu's default .bashrc script starts with this guard:



    # If not running interactively, don't do anything
    
case $- in
    
    *i*) ;;
    
      *) return;;
    
esac


    Any lines you add below this will not be loaded by your cron script because cronjobs do not run in an interactive environment.



    The solution: Put functions for scripts above this guard. Keep setup for the user below this guard.



    3. Load the complete user login environment



    On some systems I find its easiest to use --login to ensure the shell has the same things loaded that I have at the command line.



    * *  * * * bash --login /path/to/script.sh
    

    
* *  * * * bash --login -c "your command here"





    share|improve this answer






























      2














      1. Run the correct shell



      * *  * * * /bin/sh .....


      You are not running bash, you are running sh, so you should not expect .bashrc to be loaded!



      Try this instead:



      * *  * * * /bin/bash .....


      2. Work around Ubuntu's default .bashrc



      Another problem might be that Ubuntu's default .bashrc script starts with this guard:



      # If not running interactively, don't do anything
      
case $- in
      
    *i*) ;;
      
      *) return;;
      
esac


      Any lines you add below this will not be loaded by your cron script because cronjobs do not run in an interactive environment.



      The solution: Put functions for scripts above this guard. Keep setup for the user below this guard.



      3. Load the complete user login environment



      On some systems I find its easiest to use --login to ensure the shell has the same things loaded that I have at the command line.



      * *  * * * bash --login /path/to/script.sh
      

      
* *  * * * bash --login -c "your command here"





      share|improve this answer




























        2












        2








        2







        1. Run the correct shell



        * *  * * * /bin/sh .....


        You are not running bash, you are running sh, so you should not expect .bashrc to be loaded!



        Try this instead:



        * *  * * * /bin/bash .....


        2. Work around Ubuntu's default .bashrc



        Another problem might be that Ubuntu's default .bashrc script starts with this guard:



        # If not running interactively, don't do anything
        
case $- in
        
    *i*) ;;
        
      *) return;;
        
esac


        Any lines you add below this will not be loaded by your cron script because cronjobs do not run in an interactive environment.



        The solution: Put functions for scripts above this guard. Keep setup for the user below this guard.



        3. Load the complete user login environment



        On some systems I find its easiest to use --login to ensure the shell has the same things loaded that I have at the command line.



        * *  * * * bash --login /path/to/script.sh
        

        
* *  * * * bash --login -c "your command here"





        share|improve this answer















        1. Run the correct shell



        * *  * * * /bin/sh .....


        You are not running bash, you are running sh, so you should not expect .bashrc to be loaded!



        Try this instead:



        * *  * * * /bin/bash .....


        2. Work around Ubuntu's default .bashrc



        Another problem might be that Ubuntu's default .bashrc script starts with this guard:



        # If not running interactively, don't do anything
        
case $- in
        
    *i*) ;;
        
      *) return;;
        
esac


        Any lines you add below this will not be loaded by your cron script because cronjobs do not run in an interactive environment.



        The solution: Put functions for scripts above this guard. Keep setup for the user below this guard.



        3. Load the complete user login environment



        On some systems I find its easiest to use --login to ensure the shell has the same things loaded that I have at the command line.



        * *  * * * bash --login /path/to/script.sh
        

        
* *  * * * bash --login -c "your command here"






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Feb 26 at 6:29

























        answered Oct 4 '18 at 8:30









        joeytwiddlejoeytwiddle

        1,0241021




        1,0241021






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f955415%2fbashrc-shell-script-and-crontab%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

            Mouse cursor on multiple screens with different PPI

            Image
            24 6 I'm using a 4K display along with a Full HD display with both almost the same physical size and it brings some mouse cursor problems to me working with it on the default Windows settings. As the mouse movement speed depends on the pixels, it's very slow on the 4K display and very fast on the Full HD display. Is there a windows setting or application to move the mouse depending on the visible distance and not the pixels? Another problem is the virtual wall between the screens I can't move the cursor from the upper half of the 4K screen to the Full HD screen: How is it possible to virtually stretch the cursor transition area of the Full HD screen to the one of the 4K monitor? The smallest problem, nevertheless painful, is the cursor size which varies between the screens. Is there a way ...
            Read more

            Agildo Ribeiro

            Image
            Agildo Ribeiro Agildo em 2015 Nome completo Agildo da Gama Barata Ribeiro Filho Nascimento 26 de abril de 1932 Rio de Janeiro, DF Morte 28 de abril de 2018 (86 anos) Rio de Janeiro, RJ Ocupação Ator e humorista ...
            Read more

            Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”

            Image
            0 Sometime, when I try to access some menu (may be inside an application or desktop, doesn't matter), I got the following error. The menu and submenu disappear for a while. After that, I can continue using the system. And the lspci gave me the following output: $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) DeviceName: Onboard IGD Subsystem: Dell Haswell-ULT Integrated Graphics Controller Kernel driver in use: i915 unity compiz error-handling share | improve this question edited Mar 5 at 16:09 ...
            Read more