How to run logkeys












10














I just installed logkeys from Software center. I am finding it hard to run it. Its documentation page doesnt help much either.
1. How do I run it?
2. Can I bind the start up with a key combination?
3. How to see the logs?



Thanks in advance










share|improve this question





























    10














    I just installed logkeys from Software center. I am finding it hard to run it. Its documentation page doesnt help much either.
    1. How do I run it?
    2. Can I bind the start up with a key combination?
    3. How to see the logs?



    Thanks in advance










    share|improve this question



























      10












      10








      10


      5





      I just installed logkeys from Software center. I am finding it hard to run it. Its documentation page doesnt help much either.
      1. How do I run it?
      2. Can I bind the start up with a key combination?
      3. How to see the logs?



      Thanks in advance










      share|improve this question















      I just installed logkeys from Software center. I am finding it hard to run it. Its documentation page doesnt help much either.
      1. How do I run it?
      2. Can I bind the start up with a key combination?
      3. How to see the logs?



      Thanks in advance







      startup






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 18 '11 at 10:06









      Oli

      220k85558762




      220k85558762










      asked Nov 21 '10 at 16:51









      t3cht3ch

      1,09361632




      1,09361632






















          3 Answers
          3






          active

          oldest

          votes


















          6














          Add this command to startup application so logkeys will be started automatically during every startup..



          Goto-->System-->Preferences-->Startup Applications



          alt text



          In startup applications preferences click add,it will give you a windows with Name,Command and Comments..



          In Name field you can give any name and in Command field type logkeys --start and click save.



          Before that you want to specify output location for your log.In terminal type touch test.log and then type this logkeys --start --output test.log to stop logkeys type logkeys --kill in terminal.






          share|improve this answer























          • Post your comments if you have any problem,we will help you
            – karthick87
            Nov 21 '10 at 18:42










          • Karthick, test.log on my terminal isnt giving me anything.
            – t3ch
            Nov 21 '10 at 19:01










          • Do you want to view your logs?Then type tail test.log in terminal.
            – karthick87
            Nov 21 '10 at 19:06










          • Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
            – t3ch
            Nov 21 '10 at 19:08










          • Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
            – karthick87
            Nov 21 '10 at 19:21



















          4














          Logkeys quick setup:





          • Get Logkeys from GoogleCode project spot:



            wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz



          • Unarchive Logkeys:



            gunzip logkeys-0.1.1a.tar.gz 
            tar xvf logkeys-0.1.1a.tar



          • Build up Logkeys:



            cd logkeys-0.1.1a/
            ./configure
            make
            sudo make installl



          In case of ./configure failure, run:



          sudo apt-get install build-essential


          Now, it's important to have the current keyboard map file. You can download the keyboard map files at: http://code.google.com/p/logkeys/wiki/Keymaps





          • After downloading the keyboard map file that you need, you can set up logkeys:



            sudo logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log


            Where -s starts the logkeys deamon, -m is the path for the keyboard map file and -o the log output file. Logkeys should now begin to dump the capture keystrokes to the defined log file (human readable).




          • To stop logkeys:



            sudo logkeys -k



          • For auto start at boot time:



            sudo vim /etc/init.d/rc.local


            and add this to the bottom of the file:



            /usr/local/bin/logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log &



          If desired, reboot your linux box to check the auto start entry at rc.local



          sudo reboot now


          And you are done!
          Props.






          share|improve this answer























          • $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
            – Aaron Franke
            May 21 '18 at 0:26



















          0














          Sorry, I think the documentation is very understandable; Ask concrete question, if you don't understand something.



          The second question, what isn't in the docs, I can anwser with this:




          Click System > Options > Hotkeys, New hotkey, then give a name, the command is: logkeys --start --output /path/to/log(don't forget to change /path/to/log to your log location!!!), then click on your new hotkey, and give a key combination. Your thing is ready.







          share|improve this answer

















          • 1




            Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
            – t3ch
            Nov 21 '10 at 17:13












          • Ok, I'll check it once more today!
            – antivirtel
            Nov 21 '10 at 17:25











          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%2f14312%2fhow-to-run-logkeys%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          3 Answers
          3






          active

          oldest

          votes








          3 Answers
          3






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          6














          Add this command to startup application so logkeys will be started automatically during every startup..



          Goto-->System-->Preferences-->Startup Applications



          alt text



          In startup applications preferences click add,it will give you a windows with Name,Command and Comments..



          In Name field you can give any name and in Command field type logkeys --start and click save.



          Before that you want to specify output location for your log.In terminal type touch test.log and then type this logkeys --start --output test.log to stop logkeys type logkeys --kill in terminal.






          share|improve this answer























          • Post your comments if you have any problem,we will help you
            – karthick87
            Nov 21 '10 at 18:42










          • Karthick, test.log on my terminal isnt giving me anything.
            – t3ch
            Nov 21 '10 at 19:01










          • Do you want to view your logs?Then type tail test.log in terminal.
            – karthick87
            Nov 21 '10 at 19:06










          • Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
            – t3ch
            Nov 21 '10 at 19:08










          • Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
            – karthick87
            Nov 21 '10 at 19:21
















          6














          Add this command to startup application so logkeys will be started automatically during every startup..



          Goto-->System-->Preferences-->Startup Applications



          alt text



          In startup applications preferences click add,it will give you a windows with Name,Command and Comments..



          In Name field you can give any name and in Command field type logkeys --start and click save.



          Before that you want to specify output location for your log.In terminal type touch test.log and then type this logkeys --start --output test.log to stop logkeys type logkeys --kill in terminal.






          share|improve this answer























          • Post your comments if you have any problem,we will help you
            – karthick87
            Nov 21 '10 at 18:42










          • Karthick, test.log on my terminal isnt giving me anything.
            – t3ch
            Nov 21 '10 at 19:01










          • Do you want to view your logs?Then type tail test.log in terminal.
            – karthick87
            Nov 21 '10 at 19:06










          • Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
            – t3ch
            Nov 21 '10 at 19:08










          • Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
            – karthick87
            Nov 21 '10 at 19:21














          6












          6








          6






          Add this command to startup application so logkeys will be started automatically during every startup..



          Goto-->System-->Preferences-->Startup Applications



          alt text



          In startup applications preferences click add,it will give you a windows with Name,Command and Comments..



          In Name field you can give any name and in Command field type logkeys --start and click save.



          Before that you want to specify output location for your log.In terminal type touch test.log and then type this logkeys --start --output test.log to stop logkeys type logkeys --kill in terminal.






          share|improve this answer














          Add this command to startup application so logkeys will be started automatically during every startup..



          Goto-->System-->Preferences-->Startup Applications



          alt text



          In startup applications preferences click add,it will give you a windows with Name,Command and Comments..



          In Name field you can give any name and in Command field type logkeys --start and click save.



          Before that you want to specify output location for your log.In terminal type touch test.log and then type this logkeys --start --output test.log to stop logkeys type logkeys --kill in terminal.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 14 '12 at 10:37









          komputes

          1,88552229




          1,88552229










          answered Nov 21 '10 at 17:25









          karthick87karthick87

          47.7k53166217




          47.7k53166217












          • Post your comments if you have any problem,we will help you
            – karthick87
            Nov 21 '10 at 18:42










          • Karthick, test.log on my terminal isnt giving me anything.
            – t3ch
            Nov 21 '10 at 19:01










          • Do you want to view your logs?Then type tail test.log in terminal.
            – karthick87
            Nov 21 '10 at 19:06










          • Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
            – t3ch
            Nov 21 '10 at 19:08










          • Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
            – karthick87
            Nov 21 '10 at 19:21


















          • Post your comments if you have any problem,we will help you
            – karthick87
            Nov 21 '10 at 18:42










          • Karthick, test.log on my terminal isnt giving me anything.
            – t3ch
            Nov 21 '10 at 19:01










          • Do you want to view your logs?Then type tail test.log in terminal.
            – karthick87
            Nov 21 '10 at 19:06










          • Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
            – t3ch
            Nov 21 '10 at 19:08










          • Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
            – karthick87
            Nov 21 '10 at 19:21
















          Post your comments if you have any problem,we will help you
          – karthick87
          Nov 21 '10 at 18:42




          Post your comments if you have any problem,we will help you
          – karthick87
          Nov 21 '10 at 18:42












          Karthick, test.log on my terminal isnt giving me anything.
          – t3ch
          Nov 21 '10 at 19:01




          Karthick, test.log on my terminal isnt giving me anything.
          – t3ch
          Nov 21 '10 at 19:01












          Do you want to view your logs?Then type tail test.log in terminal.
          – karthick87
          Nov 21 '10 at 19:06




          Do you want to view your logs?Then type tail test.log in terminal.
          – karthick87
          Nov 21 '10 at 19:06












          Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
          – t3ch
          Nov 21 '10 at 19:08




          Karthick, this is what I am getting. ubuntu@ubuntu-XPS-M1330:~$ tail test.log tail: cannot open `test.log' for reading: No such file or directory
          – t3ch
          Nov 21 '10 at 19:08












          Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
          – karthick87
          Nov 21 '10 at 19:21




          Uh there is no test.log file..I told you to create a file in the name test.log.To create type touch test.log in terminal.And then type this logkeys --start --output test.log
          – karthick87
          Nov 21 '10 at 19:21













          4














          Logkeys quick setup:





          • Get Logkeys from GoogleCode project spot:



            wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz



          • Unarchive Logkeys:



            gunzip logkeys-0.1.1a.tar.gz 
            tar xvf logkeys-0.1.1a.tar



          • Build up Logkeys:



            cd logkeys-0.1.1a/
            ./configure
            make
            sudo make installl



          In case of ./configure failure, run:



          sudo apt-get install build-essential


          Now, it's important to have the current keyboard map file. You can download the keyboard map files at: http://code.google.com/p/logkeys/wiki/Keymaps





          • After downloading the keyboard map file that you need, you can set up logkeys:



            sudo logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log


            Where -s starts the logkeys deamon, -m is the path for the keyboard map file and -o the log output file. Logkeys should now begin to dump the capture keystrokes to the defined log file (human readable).




          • To stop logkeys:



            sudo logkeys -k



          • For auto start at boot time:



            sudo vim /etc/init.d/rc.local


            and add this to the bottom of the file:



            /usr/local/bin/logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log &



          If desired, reboot your linux box to check the auto start entry at rc.local



          sudo reboot now


          And you are done!
          Props.






          share|improve this answer























          • $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
            – Aaron Franke
            May 21 '18 at 0:26
















          4














          Logkeys quick setup:





          • Get Logkeys from GoogleCode project spot:



            wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz



          • Unarchive Logkeys:



            gunzip logkeys-0.1.1a.tar.gz 
            tar xvf logkeys-0.1.1a.tar



          • Build up Logkeys:



            cd logkeys-0.1.1a/
            ./configure
            make
            sudo make installl



          In case of ./configure failure, run:



          sudo apt-get install build-essential


          Now, it's important to have the current keyboard map file. You can download the keyboard map files at: http://code.google.com/p/logkeys/wiki/Keymaps





          • After downloading the keyboard map file that you need, you can set up logkeys:



            sudo logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log


            Where -s starts the logkeys deamon, -m is the path for the keyboard map file and -o the log output file. Logkeys should now begin to dump the capture keystrokes to the defined log file (human readable).




          • To stop logkeys:



            sudo logkeys -k



          • For auto start at boot time:



            sudo vim /etc/init.d/rc.local


            and add this to the bottom of the file:



            /usr/local/bin/logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log &



          If desired, reboot your linux box to check the auto start entry at rc.local



          sudo reboot now


          And you are done!
          Props.






          share|improve this answer























          • $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
            – Aaron Franke
            May 21 '18 at 0:26














          4












          4








          4






          Logkeys quick setup:





          • Get Logkeys from GoogleCode project spot:



            wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz



          • Unarchive Logkeys:



            gunzip logkeys-0.1.1a.tar.gz 
            tar xvf logkeys-0.1.1a.tar



          • Build up Logkeys:



            cd logkeys-0.1.1a/
            ./configure
            make
            sudo make installl



          In case of ./configure failure, run:



          sudo apt-get install build-essential


          Now, it's important to have the current keyboard map file. You can download the keyboard map files at: http://code.google.com/p/logkeys/wiki/Keymaps





          • After downloading the keyboard map file that you need, you can set up logkeys:



            sudo logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log


            Where -s starts the logkeys deamon, -m is the path for the keyboard map file and -o the log output file. Logkeys should now begin to dump the capture keystrokes to the defined log file (human readable).




          • To stop logkeys:



            sudo logkeys -k



          • For auto start at boot time:



            sudo vim /etc/init.d/rc.local


            and add this to the bottom of the file:



            /usr/local/bin/logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log &



          If desired, reboot your linux box to check the auto start entry at rc.local



          sudo reboot now


          And you are done!
          Props.






          share|improve this answer














          Logkeys quick setup:





          • Get Logkeys from GoogleCode project spot:



            wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz



          • Unarchive Logkeys:



            gunzip logkeys-0.1.1a.tar.gz 
            tar xvf logkeys-0.1.1a.tar



          • Build up Logkeys:



            cd logkeys-0.1.1a/
            ./configure
            make
            sudo make installl



          In case of ./configure failure, run:



          sudo apt-get install build-essential


          Now, it's important to have the current keyboard map file. You can download the keyboard map files at: http://code.google.com/p/logkeys/wiki/Keymaps





          • After downloading the keyboard map file that you need, you can set up logkeys:



            sudo logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log


            Where -s starts the logkeys deamon, -m is the path for the keyboard map file and -o the log output file. Logkeys should now begin to dump the capture keystrokes to the defined log file (human readable).




          • To stop logkeys:



            sudo logkeys -k



          • For auto start at boot time:



            sudo vim /etc/init.d/rc.local


            and add this to the bottom of the file:



            /usr/local/bin/logkeys -s -m /home/XYZ/Downloads/de.map -o /home/XYZ/loggy.log &



          If desired, reboot your linux box to check the auto start entry at rc.local



          sudo reboot now


          And you are done!
          Props.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 25 '13 at 16:44









          Aditya

          9,228125589




          9,228125589










          answered Jan 25 '13 at 15:38









          undertugaundertuga

          26924




          26924












          • $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
            – Aaron Franke
            May 21 '18 at 0:26


















          • $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
            – Aaron Franke
            May 21 '18 at 0:26
















          $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
          – Aaron Franke
          May 21 '18 at 0:26




          $ wget http://logkeys.googlecode.com/files/logkeys-0.1.1a.tar.gz gives 404 Not Found.
          – Aaron Franke
          May 21 '18 at 0:26











          0














          Sorry, I think the documentation is very understandable; Ask concrete question, if you don't understand something.



          The second question, what isn't in the docs, I can anwser with this:




          Click System > Options > Hotkeys, New hotkey, then give a name, the command is: logkeys --start --output /path/to/log(don't forget to change /path/to/log to your log location!!!), then click on your new hotkey, and give a key combination. Your thing is ready.







          share|improve this answer

















          • 1




            Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
            – t3ch
            Nov 21 '10 at 17:13












          • Ok, I'll check it once more today!
            – antivirtel
            Nov 21 '10 at 17:25
















          0














          Sorry, I think the documentation is very understandable; Ask concrete question, if you don't understand something.



          The second question, what isn't in the docs, I can anwser with this:




          Click System > Options > Hotkeys, New hotkey, then give a name, the command is: logkeys --start --output /path/to/log(don't forget to change /path/to/log to your log location!!!), then click on your new hotkey, and give a key combination. Your thing is ready.







          share|improve this answer

















          • 1




            Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
            – t3ch
            Nov 21 '10 at 17:13












          • Ok, I'll check it once more today!
            – antivirtel
            Nov 21 '10 at 17:25














          0












          0








          0






          Sorry, I think the documentation is very understandable; Ask concrete question, if you don't understand something.



          The second question, what isn't in the docs, I can anwser with this:




          Click System > Options > Hotkeys, New hotkey, then give a name, the command is: logkeys --start --output /path/to/log(don't forget to change /path/to/log to your log location!!!), then click on your new hotkey, and give a key combination. Your thing is ready.







          share|improve this answer












          Sorry, I think the documentation is very understandable; Ask concrete question, if you don't understand something.



          The second question, what isn't in the docs, I can anwser with this:




          Click System > Options > Hotkeys, New hotkey, then give a name, the command is: logkeys --start --output /path/to/log(don't forget to change /path/to/log to your log location!!!), then click on your new hotkey, and give a key combination. Your thing is ready.








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 21 '10 at 17:12









          antivirtelantivirtel

          2,72742546




          2,72742546








          • 1




            Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
            – t3ch
            Nov 21 '10 at 17:13












          • Ok, I'll check it once more today!
            – antivirtel
            Nov 21 '10 at 17:25














          • 1




            Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
            – t3ch
            Nov 21 '10 at 17:13












          • Ok, I'll check it once more today!
            – antivirtel
            Nov 21 '10 at 17:25








          1




          1




          Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
          – t3ch
          Nov 21 '10 at 17:13






          Thanks B.Roland. I am going through documentation .. and will edit the question accordingly.
          – t3ch
          Nov 21 '10 at 17:13














          Ok, I'll check it once more today!
          – antivirtel
          Nov 21 '10 at 17:25




          Ok, I'll check it once more today!
          – antivirtel
          Nov 21 '10 at 17:25


















          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.





          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%2faskubuntu.com%2fquestions%2f14312%2fhow-to-run-logkeys%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

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

          Eduardo VII do Reino Unido