grep --exclude option doesn't always skip named pipes












0















I have a directory that contains, among other files, 3 named pipes: FIFO, FIFO1, and FIFO11. If I try something like



grep mypattern *


in this directory, grep hangs forever on the named pipes, so I need to exclude them. Unexpectedly,



grep --exclude='FIF*' mypattern *


does not solve the problem; grep still hangs forever. However,



grep -r --exclude='FIF*' mypattern .


does solve the hanging problem (albeit with the undesired side effect of searching all the subdirectories).



I did some testing that shows that grep --exclude ='FIF*' mypattern * works as expected if FIFO etc. are regular files, not named pipes.



Question 1: Why does grep skip --excludes in both cases if they're regular files, and skips --excluded named pipes in the recursive case, but doesn't skip named pipes in the non-recursive case?



Question 2: Is there another way to format the exclusion that will skip these files in all cases?



Question 3: is there a better way to accomplish what I'm after?









share







New contributor




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

























    0















    I have a directory that contains, among other files, 3 named pipes: FIFO, FIFO1, and FIFO11. If I try something like



    grep mypattern *


    in this directory, grep hangs forever on the named pipes, so I need to exclude them. Unexpectedly,



    grep --exclude='FIF*' mypattern *


    does not solve the problem; grep still hangs forever. However,



    grep -r --exclude='FIF*' mypattern .


    does solve the hanging problem (albeit with the undesired side effect of searching all the subdirectories).



    I did some testing that shows that grep --exclude ='FIF*' mypattern * works as expected if FIFO etc. are regular files, not named pipes.



    Question 1: Why does grep skip --excludes in both cases if they're regular files, and skips --excluded named pipes in the recursive case, but doesn't skip named pipes in the non-recursive case?



    Question 2: Is there another way to format the exclusion that will skip these files in all cases?



    Question 3: is there a better way to accomplish what I'm after?









    share







    New contributor




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























      0












      0








      0








      I have a directory that contains, among other files, 3 named pipes: FIFO, FIFO1, and FIFO11. If I try something like



      grep mypattern *


      in this directory, grep hangs forever on the named pipes, so I need to exclude them. Unexpectedly,



      grep --exclude='FIF*' mypattern *


      does not solve the problem; grep still hangs forever. However,



      grep -r --exclude='FIF*' mypattern .


      does solve the hanging problem (albeit with the undesired side effect of searching all the subdirectories).



      I did some testing that shows that grep --exclude ='FIF*' mypattern * works as expected if FIFO etc. are regular files, not named pipes.



      Question 1: Why does grep skip --excludes in both cases if they're regular files, and skips --excluded named pipes in the recursive case, but doesn't skip named pipes in the non-recursive case?



      Question 2: Is there another way to format the exclusion that will skip these files in all cases?



      Question 3: is there a better way to accomplish what I'm after?









      share







      New contributor




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












      I have a directory that contains, among other files, 3 named pipes: FIFO, FIFO1, and FIFO11. If I try something like



      grep mypattern *


      in this directory, grep hangs forever on the named pipes, so I need to exclude them. Unexpectedly,



      grep --exclude='FIF*' mypattern *


      does not solve the problem; grep still hangs forever. However,



      grep -r --exclude='FIF*' mypattern .


      does solve the hanging problem (albeit with the undesired side effect of searching all the subdirectories).



      I did some testing that shows that grep --exclude ='FIF*' mypattern * works as expected if FIFO etc. are regular files, not named pipes.



      Question 1: Why does grep skip --excludes in both cases if they're regular files, and skips --excluded named pipes in the recursive case, but doesn't skip named pipes in the non-recursive case?



      Question 2: Is there another way to format the exclusion that will skip these files in all cases?



      Question 3: is there a better way to accomplish what I'm after?







      grep





      share







      New contributor




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










      share







      New contributor




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








      share



      share






      New contributor




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









      asked 4 mins ago









      rasras

      1




      1




      New contributor




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





      New contributor





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






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






















          0






          active

          oldest

          votes











          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',
          autoActivateHeartbeat: false,
          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
          });


          }
          });






          ras 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%2funix.stackexchange.com%2fquestions%2f499229%2fgrep-exclude-option-doesnt-always-skip-named-pipes%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








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










          draft saved

          draft discarded


















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













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












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
















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499229%2fgrep-exclude-option-doesnt-always-skip-named-pipes%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

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt