conditional find output missing












2















Im trying to build a conditional statement to search for files of a certain size (in this case 1Gb. 



if [ "find /location/sub/int/ -size +1G" ]

then

  > /location/sub/int/large_file_audit.txt

fi


I run this and it creates a file but the file is empty, how can I get the results of the find to populate into the file? what am I doing wrong?






command-line bash find







share|improve this question









New contributor




Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    2















    Im trying to build a conditional statement to search for files of a certain size (in this case 1Gb. 



    if [ "find /location/sub/int/ -size +1G" ]
    
then
    
  > /location/sub/int/large_file_audit.txt
    
fi


    I run this and it creates a file but the file is empty, how can I get the results of the find to populate into the file? what am I doing wrong?






    command-line bash find







    share|improve this question









    New contributor




    Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      2












      2








      2








      Im trying to build a conditional statement to search for files of a certain size (in this case 1Gb. 



      if [ "find /location/sub/int/ -size +1G" ]
      
then
      
  > /location/sub/int/large_file_audit.txt
      
fi


      I run this and it creates a file but the file is empty, how can I get the results of the find to populate into the file? what am I doing wrong?






      command-line bash find







      share|improve this question









      New contributor




      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      Im trying to build a conditional statement to search for files of a certain size (in this case 1Gb. 



      if [ "find /location/sub/int/ -size +1G" ]
      
then
      
  > /location/sub/int/large_file_audit.txt
      
fi


      I run this and it creates a file but the file is empty, how can I get the results of the find to populate into the file? what am I doing wrong?






      command-line bash find




      command-line bash find






      share|improve this question









      New contributor




      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 6 hours ago









      Ravexina

      32k1482112




      32k1482112






      New contributor




      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 7 hours ago









      ShadwarShadwar

      111




      111




      New contributor




      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Shadwar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          2 Answers
          2






          active

          oldest

          votes


















          3














          Your test if [ "find /location/sub/int/ -size +1G" ] doesn't work the way you intend because it tests the non-emptiness of the string "find /location/sub/int/ -size +1G" - which will always be true. In any case, the redirection > /location/sub/int/large_file_audit.txt will not magically pick up the standard output of the preceding command, so will always create an empty file.



          Perhaps the closest to your intent in Bash would be to put the results of find into an array, and then test whether it has any elements:



          mapfile -t files < <(find /location/sub/int/ -size +1G)
          

          
if (( ${#files[@] > 0 )); then 
          
  printf '%sn' "${files[@]}" > /location/sub/int/large_file_audit.txt
          
fi


          This won't gracefully handle filenames containing newlines - with newer versions of bash, you could make the find and mapfile null-delimited, but there's not much benefit if you're outputting them as a newline-delimited list anyhow.






          share|improve this answer































            2














            One liner workaround:



            find -size +10G | grep ".*" > file.log || (rm file.log; echo "Can't find anything")


            Or:



            find -size +10G | grep ".*" > file.log || rm file.log



            Note that find returns 1 (False) when files are not processed correctly for any reason, so I suggest using something like:



            #!/bin/bash
            
RESULTS=$(find /path -size +1G)
            
if [ -n "$RESULTS" ];
            
 then
            
   echo "$RESULTS" > /path/file.log
            
fi


            First run the find and put the results in a variable, then if the variable contained anything save that into a log file.






            share|improve this answer





















            • 2





              While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

              – Sergiy Kolodyazhnyy
              5 hours ago






            • 1





              find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

              – Xen2050
              1 hour ago











            • @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

              – Sergiy Kolodyazhnyy
              11 mins ago











            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
            });


            }
            });






            Shadwar is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110989%2fconditional-find-output-missing%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









            3














            Your test if [ "find /location/sub/int/ -size +1G" ] doesn't work the way you intend because it tests the non-emptiness of the string "find /location/sub/int/ -size +1G" - which will always be true. In any case, the redirection > /location/sub/int/large_file_audit.txt will not magically pick up the standard output of the preceding command, so will always create an empty file.



            Perhaps the closest to your intent in Bash would be to put the results of find into an array, and then test whether it has any elements:



            mapfile -t files < <(find /location/sub/int/ -size +1G)
            

            
if (( ${#files[@] > 0 )); then 
            
  printf '%sn' "${files[@]}" > /location/sub/int/large_file_audit.txt
            
fi


            This won't gracefully handle filenames containing newlines - with newer versions of bash, you could make the find and mapfile null-delimited, but there's not much benefit if you're outputting them as a newline-delimited list anyhow.






            share|improve this answer




























              3














              Your test if [ "find /location/sub/int/ -size +1G" ] doesn't work the way you intend because it tests the non-emptiness of the string "find /location/sub/int/ -size +1G" - which will always be true. In any case, the redirection > /location/sub/int/large_file_audit.txt will not magically pick up the standard output of the preceding command, so will always create an empty file.



              Perhaps the closest to your intent in Bash would be to put the results of find into an array, and then test whether it has any elements:



              mapfile -t files < <(find /location/sub/int/ -size +1G)
              

              
if (( ${#files[@] > 0 )); then 
              
  printf '%sn' "${files[@]}" > /location/sub/int/large_file_audit.txt
              
fi


              This won't gracefully handle filenames containing newlines - with newer versions of bash, you could make the find and mapfile null-delimited, but there's not much benefit if you're outputting them as a newline-delimited list anyhow.






              share|improve this answer


























                3












                3








                3







                Your test if [ "find /location/sub/int/ -size +1G" ] doesn't work the way you intend because it tests the non-emptiness of the string "find /location/sub/int/ -size +1G" - which will always be true. In any case, the redirection > /location/sub/int/large_file_audit.txt will not magically pick up the standard output of the preceding command, so will always create an empty file.



                Perhaps the closest to your intent in Bash would be to put the results of find into an array, and then test whether it has any elements:



                mapfile -t files < <(find /location/sub/int/ -size +1G)
                

                
if (( ${#files[@] > 0 )); then 
                
  printf '%sn' "${files[@]}" > /location/sub/int/large_file_audit.txt
                
fi


                This won't gracefully handle filenames containing newlines - with newer versions of bash, you could make the find and mapfile null-delimited, but there's not much benefit if you're outputting them as a newline-delimited list anyhow.






                share|improve this answer













                Your test if [ "find /location/sub/int/ -size +1G" ] doesn't work the way you intend because it tests the non-emptiness of the string "find /location/sub/int/ -size +1G" - which will always be true. In any case, the redirection > /location/sub/int/large_file_audit.txt will not magically pick up the standard output of the preceding command, so will always create an empty file.



                Perhaps the closest to your intent in Bash would be to put the results of find into an array, and then test whether it has any elements:



                mapfile -t files < <(find /location/sub/int/ -size +1G)
                

                
if (( ${#files[@] > 0 )); then 
                
  printf '%sn' "${files[@]}" > /location/sub/int/large_file_audit.txt
                
fi


                This won't gracefully handle filenames containing newlines - with newer versions of bash, you could make the find and mapfile null-delimited, but there's not much benefit if you're outputting them as a newline-delimited list anyhow.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 5 hours ago









                steeldriversteeldriver

                66.5k11107179




                66.5k11107179

























                    2














                    One liner workaround:



                    find -size +10G | grep ".*" > file.log || (rm file.log; echo "Can't find anything")


                    Or:



                    find -size +10G | grep ".*" > file.log || rm file.log



                    Note that find returns 1 (False) when files are not processed correctly for any reason, so I suggest using something like:



                    #!/bin/bash
                    
RESULTS=$(find /path -size +1G)
                    
if [ -n "$RESULTS" ];
                    
 then
                    
   echo "$RESULTS" > /path/file.log
                    
fi


                    First run the find and put the results in a variable, then if the variable contained anything save that into a log file.






                    share|improve this answer





















                    • 2





                      While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

                      – Sergiy Kolodyazhnyy
                      5 hours ago






                    • 1





                      find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

                      – Xen2050
                      1 hour ago











                    • @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

                      – Sergiy Kolodyazhnyy
                      11 mins ago
















                    2














                    One liner workaround:



                    find -size +10G | grep ".*" > file.log || (rm file.log; echo "Can't find anything")


                    Or:



                    find -size +10G | grep ".*" > file.log || rm file.log



                    Note that find returns 1 (False) when files are not processed correctly for any reason, so I suggest using something like:



                    #!/bin/bash
                    
RESULTS=$(find /path -size +1G)
                    
if [ -n "$RESULTS" ];
                    
 then
                    
   echo "$RESULTS" > /path/file.log
                    
fi


                    First run the find and put the results in a variable, then if the variable contained anything save that into a log file.






                    share|improve this answer





















                    • 2





                      While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

                      – Sergiy Kolodyazhnyy
                      5 hours ago






                    • 1





                      find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

                      – Xen2050
                      1 hour ago











                    • @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

                      – Sergiy Kolodyazhnyy
                      11 mins ago














                    2












                    2








                    2







                    One liner workaround:



                    find -size +10G | grep ".*" > file.log || (rm file.log; echo "Can't find anything")


                    Or:



                    find -size +10G | grep ".*" > file.log || rm file.log



                    Note that find returns 1 (False) when files are not processed correctly for any reason, so I suggest using something like:



                    #!/bin/bash
                    
RESULTS=$(find /path -size +1G)
                    
if [ -n "$RESULTS" ];
                    
 then
                    
   echo "$RESULTS" > /path/file.log
                    
fi


                    First run the find and put the results in a variable, then if the variable contained anything save that into a log file.






                    share|improve this answer















                    One liner workaround:



                    find -size +10G | grep ".*" > file.log || (rm file.log; echo "Can't find anything")


                    Or:



                    find -size +10G | grep ".*" > file.log || rm file.log



                    Note that find returns 1 (False) when files are not processed correctly for any reason, so I suggest using something like:



                    #!/bin/bash
                    
RESULTS=$(find /path -size +1G)
                    
if [ -n "$RESULTS" ];
                    
 then
                    
   echo "$RESULTS" > /path/file.log
                    
fi


                    First run the find and put the results in a variable, then if the variable contained anything save that into a log file.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited 10 mins ago









                    Sergiy Kolodyazhnyy

                    71k9147312




                    71k9147312










                    answered 7 hours ago









                    RavexinaRavexina

                    32k1482112




                    32k1482112








                    • 2





                      While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

                      – Sergiy Kolodyazhnyy
                      5 hours ago






                    • 1





                      find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

                      – Xen2050
                      1 hour ago











                    • @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

                      – Sergiy Kolodyazhnyy
                      11 mins ago














                    • 2





                      While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

                      – Sergiy Kolodyazhnyy
                      5 hours ago






                    • 1





                      find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

                      – Xen2050
                      1 hour ago











                    • @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

                      – Sergiy Kolodyazhnyy
                      11 mins ago








                    2




                    2





                    While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

                    – Sergiy Kolodyazhnyy
                    5 hours ago





                    While the answer is all correct, you might want to touch on why original if [ "find /location/sub/int/ -size +1G" ] does not work as intended ( and what it actually does instead of what user expects ).

                    – Sergiy Kolodyazhnyy
                    5 hours ago




                    1




                    1





                    find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

                    – Xen2050
                    1 hour ago





                    find returns 1 if I ask it to look somewhere that doesn't exist, but if the path exists but -size finds nothing, it does return 0. (and 1 is false).

                    – Xen2050
                    1 hour ago













                    @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

                    – Sergiy Kolodyazhnyy
                    11 mins ago





                    @Xen2050 To be exact , find returns 1 for any case where directory entries were not processed correctly as stated in EXIT STATUS part of the manual, which includes permission denied error on subdirectories or parent directory (try with chmod -r or touch testdir/subdir/foobar2;chmod -x testdir ).

                    – Sergiy Kolodyazhnyy
                    11 mins ago










                    Shadwar is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    Shadwar is a new contributor. Be nice, and check out our Code of Conduct.













                    Shadwar is a new contributor. Be nice, and check out our Code of Conduct.












                    Shadwar is a new contributor. Be nice, and check out our Code of Conduct.
















                    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%2f1110989%2fconditional-find-output-missing%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

                    What other Star Trek series did the main TNG cast show up in?

                    Image
                    .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 4 I'm referring to Picard, Riker, Data, Worf, Geordi, Dr. Crusher, Wesley Crusher, Chief O'Brien and family, Deanna Troi, Guinan. I know Picard and Worf show up on DS9, though I haven't seen it myself. I'm curious what happened to the characters after that last episode of TNG? star-trek star-trek-tng share | improve this question edited 10 hours ago Ham Sandwich 6,051 2 25 75 ...
                    Read more

                    Berlina muro

                    Image
                    La berlina muro ĉe Bethaniendamm, 1986 La berlina muro aŭ simple la muro [1] , nomita ankaŭ "kontraŭfaŝisma remparo" en propaganda lingvo de la iama Germana Demokratia Respubliko, estis parto de la interngermana limo, kiu dividis de la 13-a de aŭgusto 1961 ĝis la 9-a de novembro 1989 okcidentan Berlinon de la orienta parto de la urbo kaj de la ĉirkaŭa tereno de la GDR. Ĝi estis unu el la plej famaj simboloj de la malvarma milito kaj de la disdivido de Germanio. Pli ol simpla muro, la berlina muro estis fakte tuta defendokonstruaĵo kun du muroj, ena malplena strio, rondirvojo, gardturoj kaj alarmsistemoj. Dum la provo transiri la severe garditan limon al okcidenta Berlino multaj homoj estis mortigitaj. La preciza nombro de viktimoj estas pridisputita kaj ne certa; la nombroj anoncataj varias inter 86 kaj 238 mortintoj. La malplifortiĝo de Sovetunio kaj la politiko de liberigo gvidita de Miĥail Gorbaĉov ebligis al la orientgermanoj faligi la 9-an de novembro 1989 l...
                    Read more

                    Berlina aerponto

                    Image
                    Flugkoridoroj dum la blokado de Berlino La Berlina aerponto estas la provizigo de okcidenta Berlino per aviadiloj fare de la aliancanoj inter la 23-a de junio 1948 kaj la 12-a de majo 1949 dum la blokado de Berlino fare de la sovetia armeo. Enhavo 1 Historio 1.1 La aerkoridoroj 1.2 Unuaj flugoj 1.3 Plibonigo de la aerponto 1.4 Fino de la aerponto 1.5 Rozinbombiloj 1.6 Bilanco 2 Flughavenoj 2.1 Berlino 2.2 Okcidenta Germanio 3 Aviadiloj de la berlina aerponto 4 15-a datreveno de la aerponto 5 Bibliografio 6 Referencoj 7 Eksteraj ligiloj Historio | General Lucius D. Clay, militguberniestro de la usona okupadzono Jam antaŭ la berlina aerponto estiĝis la malgranda aerponto . La estro de la sovetia militadministracio en Germanio, Vasili Daniloviĉ Sokolovski, ordonis la 1-an de aprilo 1948, kiel reago al la konferenco de Londono inter britoj, francoj kaj reprezentantoj de Benelukso pri aligo de Germa...
                    Read more