Temporarily declare a variable in Bash











up vote
0
down vote

favorite












To declare a variable in Bash (say in a Bash script-file and not in Bash function) I do for example:



x=y


But when I finish using it inside that script-file I do unset x.



Is there a way (without using a function), to unset the variable after say 5 minutes, both in one line?



A plausible approach might be x=y && echo "unset x" | at now + 5 minutes.






bash variable at







share|improve this question


















  • 1




    You need to do unset x only if you are sourcing the script file. Otherwise the script runs in a subshell and does not affect your shell environment, so you don't need to unset it. I use parentheses to run one-liners with temporary variables on the command line all the time, like ( for i in {1..20}; do dosomething; done), and after I execute this command I don't have $i in my shell.
    – Weijun Zhou
    1 hour ago










  • If you're trying to do that for "security" purposes (ie. that var holds a password), then keep in mind that unsetting a variable does not guarantee in any way that its content will be scrubbed from memory. Simply put, keeping sensitive data in plain text in shell variables is not something that should be done for 5 secs, 5 minutes or 5 hours.
    – pizdelect
    22 mins ago

















up vote
0
down vote

favorite












To declare a variable in Bash (say in a Bash script-file and not in Bash function) I do for example:



x=y


But when I finish using it inside that script-file I do unset x.



Is there a way (without using a function), to unset the variable after say 5 minutes, both in one line?



A plausible approach might be x=y && echo "unset x" | at now + 5 minutes.






bash variable at







share|improve this question


















  • 1




    You need to do unset x only if you are sourcing the script file. Otherwise the script runs in a subshell and does not affect your shell environment, so you don't need to unset it. I use parentheses to run one-liners with temporary variables on the command line all the time, like ( for i in {1..20}; do dosomething; done), and after I execute this command I don't have $i in my shell.
    – Weijun Zhou
    1 hour ago










  • If you're trying to do that for "security" purposes (ie. that var holds a password), then keep in mind that unsetting a variable does not guarantee in any way that its content will be scrubbed from memory. Simply put, keeping sensitive data in plain text in shell variables is not something that should be done for 5 secs, 5 minutes or 5 hours.
    – pizdelect
    22 mins ago















up vote
0
down vote

favorite









up vote
0
down vote

favorite











To declare a variable in Bash (say in a Bash script-file and not in Bash function) I do for example:



x=y


But when I finish using it inside that script-file I do unset x.



Is there a way (without using a function), to unset the variable after say 5 minutes, both in one line?



A plausible approach might be x=y && echo "unset x" | at now + 5 minutes.






bash variable at







share|improve this question













To declare a variable in Bash (say in a Bash script-file and not in Bash function) I do for example:



x=y


But when I finish using it inside that script-file I do unset x.



Is there a way (without using a function), to unset the variable after say 5 minutes, both in one line?



A plausible approach might be x=y && echo "unset x" | at now + 5 minutes.






bash variable at




bash variable at






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 hours ago









JohnDoea

771132




771132








  • 1




    You need to do unset x only if you are sourcing the script file. Otherwise the script runs in a subshell and does not affect your shell environment, so you don't need to unset it. I use parentheses to run one-liners with temporary variables on the command line all the time, like ( for i in {1..20}; do dosomething; done), and after I execute this command I don't have $i in my shell.
    – Weijun Zhou
    1 hour ago










  • If you're trying to do that for "security" purposes (ie. that var holds a password), then keep in mind that unsetting a variable does not guarantee in any way that its content will be scrubbed from memory. Simply put, keeping sensitive data in plain text in shell variables is not something that should be done for 5 secs, 5 minutes or 5 hours.
    – pizdelect
    22 mins ago
















  • 1




    You need to do unset x only if you are sourcing the script file. Otherwise the script runs in a subshell and does not affect your shell environment, so you don't need to unset it. I use parentheses to run one-liners with temporary variables on the command line all the time, like ( for i in {1..20}; do dosomething; done), and after I execute this command I don't have $i in my shell.
    – Weijun Zhou
    1 hour ago










  • If you're trying to do that for "security" purposes (ie. that var holds a password), then keep in mind that unsetting a variable does not guarantee in any way that its content will be scrubbed from memory. Simply put, keeping sensitive data in plain text in shell variables is not something that should be done for 5 secs, 5 minutes or 5 hours.
    – pizdelect
    22 mins ago










1




1




You need to do unset x only if you are sourcing the script file. Otherwise the script runs in a subshell and does not affect your shell environment, so you don't need to unset it. I use parentheses to run one-liners with temporary variables on the command line all the time, like ( for i in {1..20}; do dosomething; done), and after I execute this command I don't have $i in my shell.
– Weijun Zhou
1 hour ago




You need to do unset x only if you are sourcing the script file. Otherwise the script runs in a subshell and does not affect your shell environment, so you don't need to unset it. I use parentheses to run one-liners with temporary variables on the command line all the time, like ( for i in {1..20}; do dosomething; done), and after I execute this command I don't have $i in my shell.
– Weijun Zhou
1 hour ago












If you're trying to do that for "security" purposes (ie. that var holds a password), then keep in mind that unsetting a variable does not guarantee in any way that its content will be scrubbed from memory. Simply put, keeping sensitive data in plain text in shell variables is not something that should be done for 5 secs, 5 minutes or 5 hours.
– pizdelect
22 mins ago






If you're trying to do that for "security" purposes (ie. that var holds a password), then keep in mind that unsetting a variable does not guarantee in any way that its content will be scrubbed from memory. Simply put, keeping sensitive data in plain text in shell variables is not something that should be done for 5 secs, 5 minutes or 5 hours.
– pizdelect
22 mins ago












2 Answers
2






active

oldest

votes

















up vote
3
down vote













You can't use at jobs because they run in a different context, and can't affect the current shell.



But we can do something similar. This code will trigger an alarm signal, which we can catch and perform action on



#!/bin/bash



x=100



trap 'unset x' SIGALRM



mypid=$$



( /bin/sleep 3 ; kill -ALRM $mypid) &



for a in 1 2 3 4 5 6

do

  echo Now x=$x

  sleep 1

done


This example is only 3 seconds long to demonstrate the solution; you can pick your delay as you need.



In action:



Now x=100

Now x=100

Now x=100

Now x=

Now x=

Now x=


You can easily make it one line with ;...






share|improve this answer























  • Wow - great minds think alike -- and within 30 seconds of each other! :)
    – Jeff Schaller
    2 hours ago










  • @JeffSchaller I noticed that :-)
    – Stephen Harris
    2 hours ago








  • 1




    @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
    – Stephen Harris
    2 hours ago




















up vote
2
down vote













Sure:



trap 'unset x; trap - USR1' USR1; { sleep 5m; kill -USR1 $$; } &


This sets a trap on the USR1 signal, then (cheating with a semicolon to put it on one line) groups together the sleep and kill commands into a background job. When that job completes, it will send the USR1 signal to the current shell, which will execute the trap. The trap unsets x and then clears the trap.



No functions!






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f487683%2ftemporarily-declare-a-variable-in-bash%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








    up vote
    3
    down vote













    You can't use at jobs because they run in a different context, and can't affect the current shell.



    But we can do something similar. This code will trigger an alarm signal, which we can catch and perform action on



    #!/bin/bash
    

    
x=100
    

    
trap 'unset x' SIGALRM
    

    
mypid=$$
    

    
( /bin/sleep 3 ; kill -ALRM $mypid) &
    

    
for a in 1 2 3 4 5 6
    
do
    
  echo Now x=$x
    
  sleep 1
    
done


    This example is only 3 seconds long to demonstrate the solution; you can pick your delay as you need.



    In action:



    Now x=100
    
Now x=100
    
Now x=100
    
Now x=
    
Now x=
    
Now x=


    You can easily make it one line with ;...






    share|improve this answer























    • Wow - great minds think alike -- and within 30 seconds of each other! :)
      – Jeff Schaller
      2 hours ago










    • @JeffSchaller I noticed that :-)
      – Stephen Harris
      2 hours ago








    • 1




      @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
      – Stephen Harris
      2 hours ago

















    up vote
    3
    down vote













    You can't use at jobs because they run in a different context, and can't affect the current shell.



    But we can do something similar. This code will trigger an alarm signal, which we can catch and perform action on



    #!/bin/bash
    

    
x=100
    

    
trap 'unset x' SIGALRM
    

    
mypid=$$
    

    
( /bin/sleep 3 ; kill -ALRM $mypid) &
    

    
for a in 1 2 3 4 5 6
    
do
    
  echo Now x=$x
    
  sleep 1
    
done


    This example is only 3 seconds long to demonstrate the solution; you can pick your delay as you need.



    In action:



    Now x=100
    
Now x=100
    
Now x=100
    
Now x=
    
Now x=
    
Now x=


    You can easily make it one line with ;...






    share|improve this answer























    • Wow - great minds think alike -- and within 30 seconds of each other! :)
      – Jeff Schaller
      2 hours ago










    • @JeffSchaller I noticed that :-)
      – Stephen Harris
      2 hours ago








    • 1




      @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
      – Stephen Harris
      2 hours ago















    up vote
    3
    down vote










    up vote
    3
    down vote









    You can't use at jobs because they run in a different context, and can't affect the current shell.



    But we can do something similar. This code will trigger an alarm signal, which we can catch and perform action on



    #!/bin/bash
    

    
x=100
    

    
trap 'unset x' SIGALRM
    

    
mypid=$$
    

    
( /bin/sleep 3 ; kill -ALRM $mypid) &
    

    
for a in 1 2 3 4 5 6
    
do
    
  echo Now x=$x
    
  sleep 1
    
done


    This example is only 3 seconds long to demonstrate the solution; you can pick your delay as you need.



    In action:



    Now x=100
    
Now x=100
    
Now x=100
    
Now x=
    
Now x=
    
Now x=


    You can easily make it one line with ;...






    share|improve this answer














    You can't use at jobs because they run in a different context, and can't affect the current shell.



    But we can do something similar. This code will trigger an alarm signal, which we can catch and perform action on



    #!/bin/bash
    

    
x=100
    

    
trap 'unset x' SIGALRM
    

    
mypid=$$
    

    
( /bin/sleep 3 ; kill -ALRM $mypid) &
    

    
for a in 1 2 3 4 5 6
    
do
    
  echo Now x=$x
    
  sleep 1
    
done


    This example is only 3 seconds long to demonstrate the solution; you can pick your delay as you need.



    In action:



    Now x=100
    
Now x=100
    
Now x=100
    
Now x=
    
Now x=
    
Now x=


    You can easily make it one line with ;...







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 2 hours ago

























    answered 2 hours ago









    Stephen Harris

    23.9k24477




    23.9k24477












    • Wow - great minds think alike -- and within 30 seconds of each other! :)
      – Jeff Schaller
      2 hours ago










    • @JeffSchaller I noticed that :-)
      – Stephen Harris
      2 hours ago








    • 1




      @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
      – Stephen Harris
      2 hours ago




















    • Wow - great minds think alike -- and within 30 seconds of each other! :)
      – Jeff Schaller
      2 hours ago










    • @JeffSchaller I noticed that :-)
      – Stephen Harris
      2 hours ago








    • 1




      @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
      – Stephen Harris
      2 hours ago


















    Wow - great minds think alike -- and within 30 seconds of each other! :)
    – Jeff Schaller
    2 hours ago




    Wow - great minds think alike -- and within 30 seconds of each other! :)
    – Jeff Schaller
    2 hours ago












    @JeffSchaller I noticed that :-)
    – Stephen Harris
    2 hours ago






    @JeffSchaller I noticed that :-)
    – Stephen Harris
    2 hours ago






    1




    1




    @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
    – Stephen Harris
    2 hours ago






    @JeffSchaller I rolled back your edit; I specifically put a 3 second pause in as an example; a 300 second (5minute) sleep would mean the for loop won't demonstrate the solution working. I'll edit the answer to make that clear.
    – Stephen Harris
    2 hours ago














    up vote
    2
    down vote













    Sure:



    trap 'unset x; trap - USR1' USR1; { sleep 5m; kill -USR1 $$; } &


    This sets a trap on the USR1 signal, then (cheating with a semicolon to put it on one line) groups together the sleep and kill commands into a background job. When that job completes, it will send the USR1 signal to the current shell, which will execute the trap. The trap unsets x and then clears the trap.



    No functions!






    share|improve this answer



























      up vote
      2
      down vote













      Sure:



      trap 'unset x; trap - USR1' USR1; { sleep 5m; kill -USR1 $$; } &


      This sets a trap on the USR1 signal, then (cheating with a semicolon to put it on one line) groups together the sleep and kill commands into a background job. When that job completes, it will send the USR1 signal to the current shell, which will execute the trap. The trap unsets x and then clears the trap.



      No functions!






      share|improve this answer

























        up vote
        2
        down vote










        up vote
        2
        down vote









        Sure:



        trap 'unset x; trap - USR1' USR1; { sleep 5m; kill -USR1 $$; } &


        This sets a trap on the USR1 signal, then (cheating with a semicolon to put it on one line) groups together the sleep and kill commands into a background job. When that job completes, it will send the USR1 signal to the current shell, which will execute the trap. The trap unsets x and then clears the trap.



        No functions!






        share|improve this answer














        Sure:



        trap 'unset x; trap - USR1' USR1; { sleep 5m; kill -USR1 $$; } &


        This sets a trap on the USR1 signal, then (cheating with a semicolon to put it on one line) groups together the sleep and kill commands into a background job. When that job completes, it will send the USR1 signal to the current shell, which will execute the trap. The trap unsets x and then clears the trap.



        No functions!







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 2 hours ago

























        answered 2 hours ago









        Jeff Schaller

        37.6k1052121




        37.6k1052121






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f487683%2ftemporarily-declare-a-variable-in-bash%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

            Bundesstraße 106

            Image
            Dieser Artikel beschreibt die Bundesstraße 106 in Deutschland. Zur gleichnamigen Straße in Österreich siehe Mölltal Straße. Vorlage:Infobox hochrangige Straße/Wartung/DE-B Bundesstraße 106 in Deutschland Karte Basisdaten Betreiber: Deutschland  Bundesrepublik Deutschland Straßenbeginn: Wismar ( 53° 54′  N , 11° 24′  O 53.900536 11.396875 ) Straßenende: Schwerin ( 53° 36′  N , 11° 24′  O 53.592785 11.404892 ) Gesamtlänge: 40,7 km Bundesland: Mecklenburg-Vorpommern Ausbauzustand: zweistreifig [1] Bundesstraße 106 in Schwerin (Umgehungsstraße) Straßenverlauf Land Mecklenburg-Vorpommern Landkreis Nordwestmecklenburg Ortsumgehung Wismar Wallensteingraben über   Dorf Mecklenburg Wallensteingraben Groß Stieten Bad Kleinen OT Niendorf Bahnstrecke Lübeck–Bad Kleinen Zickhusen Lübstorf Klein Trebbow OT Kirch Stück
            Read more

            Verónica Boquete

            Image
            Verónica Boquete im Trikot der Nationalmannschaft (2013) Personalia Name Verónica Boquete Giadans Geburtstag 9. April 1987 Geburtsort Santiago de Compostela, Spanien Größe 159 cm Position Mittelfeld / Sturm Juniorinnen Jahre Station 2001–2005 Xuventú Aguiño Frauen Jahre Station Spiele (Tore) 1 2005–2008 Prainsa Zaragoza 83 (40) 2008–2010 Espanyol Barcelona 53 (30) 2010 Buffalo Flash 9 0 (9) 2010 Chicago Red Stars 3 0 (1) 2010–2011 Espanyol Barcelona 26 (41) 2011 Philadelphia Independence 13 0 (5) 2011 Energija Woronesch 5 0 (1) 2012–2014 Tyresö FF 39 (14) 2014 Portland Thorns FC 15 0 (4) 2014–2015 1. FFC Frankfurt 23 0 (7) 2015–2016 FC Bayern München 9 0 (0) 2016–2018 Paris Saint-Germain 31 0 (8) 2018 Peking BG Phoenix 2019– Utah Royals FC 0 0 (0) Nationalmannschaft Jahre Auswahl
            Read more

            Ida-Boy-Ed-Garten

            Image
            Die Lage des Ida-Boy-Ed-Gartens, rot markiert Der Ida-Boy-Ed-Garten Der Ida-Boy-Ed-Garten, Blick von der Wakenitzmauer durch das Tor in der Stadtmauer Der Ida-Boy-Ed-Garten ist eine Straße der Lübecker Altstadt. Inhaltsverzeichnis 1 Lage 2 Geschichte 3 Literatur 4 Weblinks Lage | Der etwa 90 Meter lange Ida-Boy-Ed-Garten befindet sich an der nördlichen Spitze der Altstadtinsel, vor dem Burgtor. Die in einem Bogen durch eine Grünanlage hangaufwärts führende Straße verbindet die Wakenitzmauer mit der Burgtorbrücke. Geschichte | Der heutige Ida-Boy-Ed-Garten wurde ursprünglich als Verlängerung der Wakenitzmauer angelegt. 1903 wurde in den erhaltenen Teil der mittelalterlichen Stadtmauer, an dem die Wakenitzmauer bei der Einmündung der Kaiserstraße begann, ein Tor mit einem großen Bogen für die Durchführung der Straße und zwei kleineren seitlichen Öffnungen für Fußgänger gebrochen, um für die neu errichteten Wohnhäuser in diesem Bereich
            Read more