Closed GoogleCodeExporter closed 9 years ago
If you want logkeys to run on system boot, you can follow directions here.
http://code.google.com/p/logkeys/wiki/Documentation#Autorun_at_system_start
What Segmentation fault are you talking about? Where did you encounter it?
Original comment by kernc...@gmail.com
on 8 Jun 2010 at 11:53
Well I use a home-made script on ubuntu 9.10 and that is almost the same... but
finally i make that work changing the directory on rc.local, i don't know why.
#!/bin/sh -e
# rc.local
cd /home/user/keyloger
./logkeys --start --keymap=/home/user/keyloger/es_ES.map
--output=/home/user/keyloger/.logkeys --device=event4
I don't know... maybe a /user/local/bin exportation needed?? because Ubuntu is
a pain in the ass on boot log, i cant remember the "segmentation fault" exactly
but on my old Debian was something on the third line of the lang.map file, any
file i try was the same. Anyway that work now... but what a crap solution...
Original comment by jotade...@gmail.com
on 8 Jun 2010 at 6:06
Yup, it's possible that the PATH variable is missing the /usr/local/bin
directory.
In rc.local, you don't need to cd, you can just run logkeys from that
directory, e.g.
# rc.local
/home/user/keyloger/logkeys --start --keymap ... ← this works
Anyway, this is not a bug and shouldn't even be a problem once a deb packet is
released.
The segfault you are referring to happened when importing invalid keymaps.
This is already fixed in the latest version.
Original comment by kernc...@gmail.com
on 8 Jun 2010 at 8:27
Original issue reported on code.google.com by
jotade...@gmail.com
on 8 Jun 2010 at 4:46