<br><br><div class="gmail_quote">2009/6/12 Paul Fertser <span dir="ltr"><<a href="mailto:fercerpav@gmail.com">fercerpav@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Michal Brzozowski <<a href="mailto:rusolis@poczta.fm">rusolis@poczta.fm</a>> writes:<br>
> Speaking about this, how to change the default behavior of the<br>
> buttons in Om2009? I know that both of them come as X events and can<br>
> be observed using xev, but the power button suspends the device even<br>
> if you're not running X, so its action is probably controlled by<br>
> power management.<br>
<br>
</div>That's oeventsd, part of FSO. You can change the behaviour by editing<br>
rules.yaml.<br>
<font color="#888888"></font></blockquote><div><br>Thanks! Is there a daemon that I can -HUP or do I need to restart for the changes to take effect?<br><br>Going back to the original point. It would be best if there was a config file where one could specify all the different keypress events (short AUX, short power, long AUX, double AUX, power-AUX, etc) and bind actions to them. The actions would be: suspend, shutdown, lock, close app, show/hide keyboard, send a custom signal to app, etc.<br>
<br>Michal<br> </div></div><br>