Modifying .bashrc to send history to syslog, problems with quotes












0















Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc



This works if I manually edit .bashrc:



export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'



Adding awk '{print $1}' causes problems, I suspect because of quotes.



This doesn't work:



export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'



Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.



Any suggestions on both of these issues?









share







New contributor




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

























    0















    Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc



    This works if I manually edit .bashrc:



    export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'



    Adding awk '{print $1}' causes problems, I suspect because of quotes.



    This doesn't work:



    export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'



    Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.



    Any suggestions on both of these issues?









    share







    New contributor




    Alex R 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








      Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc



      This works if I manually edit .bashrc:



      export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'



      Adding awk '{print $1}' causes problems, I suspect because of quotes.



      This doesn't work:



      export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'



      Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.



      Any suggestions on both of these issues?









      share







      New contributor




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












      Attempting to enable logging of bash commands to syslog, including the ip of the logged in ssh user. The end goal is to have a script which will echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc



      This works if I manually edit .bashrc:



      export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER $SSH_CONNECTION) $line"; done); trap 1 2 15;'



      Adding awk '{print $1}' causes problems, I suspect because of quotes.



      This doesn't work:



      export PROMPT_COMMAND='trap "" 1 2 15; history -a >(tee -a ~/.bash_history | while read line; do if [[ $line =~ ^#[0-9]*$ ]]; then continue; fi; logger -p local3.debug -t "bash[$$]" "($USER) $(echo $SSH_CONNECTION | awk '{print $1}') $line"; done); trap 1 2 15;'



      Attempting to wrap these quotes in the echo 'export PROMPT_COMMAND=....'' >> ~/.bashrc is also giving me a headache.



      Any suggestions on both of these issues?







      bash ubuntu bashrc





      share







      New contributor




      Alex R 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




      Alex R 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




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









      asked 8 mins ago









      Alex RAlex R

      11




      11




      New contributor




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





      New contributor





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






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


          }
          });






          Alex R 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%2f496975%2fmodifying-bashrc-to-send-history-to-syslog-problems-with-quotes%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








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










          draft saved

          draft discarded


















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













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












          Alex R 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%2f496975%2fmodifying-bashrc-to-send-history-to-syslog-problems-with-quotes%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

          Loup dans la culture

          How to solve the problem of ntp “Unable to contact time server” from KDE?

          ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux