From: Buzz <bu...@os...> - 2005-09-29 00:46:40
|
Sorry... That's what I meant to say.... "killall -HUP lircd" Buzz -----Original Message----- From: lir...@li... [mailto:lir...@li...] On Behalf Of n0dalus Sent: Thursday, 29 September 2005 12:18 AM To: Buzz Cc: lir...@li... Subject: Re: Temporarily disabling lirc output On 9/28/05, Buzz <bu...@os...> wrote: > Why not have two different lircd.conf files, one that has all remote > buttons mapped to a code, and the other that has only 1 mapped. > > * In the first file, one of the buttons has a code that triggers > irexec to run a bash script that a) copies the other lircd.conf into > place over the first and b) restarts lircd. > * In the second lircd.conf, only one button is mapped to a code at > all, and that one code triggers a very similar irexec based bash > script that a) copies the original lircd.conf back into place, and b) restarts lircd. > > That aught to do it. :-) > > Buzz. > Unfortunately if I restart lircd it will disconnect it's connection to any program using it (mplayer,xmms,etc.) I guess I can use SIGHUP to do a soft reload... would that work? n0dalus. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl |