Ubuntu lists it as:

Zeroconf LIRC daemon using input event devices
This is a small LIRC-compatible daemon that reads from /dev/input/eventX
devices and sends the received keycodes to connecting LIRC clients. Inputlircd
needs no configuration, it uses the standardised names for the keycodes as
used by the kernel. Many USB remote controls that present HID devices, as well
as multimedia keyboards should work out of the box.

Why is this good, well I just install this package and well I get full remote support – once I’ve configured the applications, which is still a pain in the arse. Now if the applications could be written to work with the zeroconfig lirc with well zero config the world will be great (well ok less un-great).

For this to work you have to:

1. Have a CPU that support Frequency Scaling
2. Have CPU Frequency scaling working
3. Use NUT (Network UPS Tools)

Here what you need to do to get thing working

• Check you what ‘Governors’ you have available
  You need to make sure the correct modules are loaded so that you can scale to the correct settings. To see what you do have loaded run:
  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
  You’ll need at least powersave and one other. Powersave should set the CPU Frequency to the lowest setting. If you don’t have powersave you’ll need to load the module. As root run:
  modprobe cpufreq_powersave and add cpufreq_powersave to the file
  /etc/modules.

  To test that it is working, ideally run something that force you CPU to 100 for a while (say compress a large folder) and then run
  cpufreq-selector --governor powersave
sleep 1
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
cpufreq-selector --governor userspace
sleep 1
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq

  The first number given should be the lowest CPU frequency and the last should be the highest (assuming the process is using a lot of CPU time still)

• Add a few new items to upssched.conf
  Using you’re favorite editor open up /etc/nut/upssched.conf and add the following line:
  AT ONBATT * START-TIMER powersave 30
AT ONLINE * CANCEL-TIMER powersave
AT ONLINE * START-TIMER userspace 30
AT ONBATT * CANCEL-TIMER userspace
  I’ve used a timer (30 seconds) to smooth out jumpy power from triggering off any actions.
• Add the command to the CMDSCRIPT file to change the CPU frequency govenor

Edit the cmdscript file (the path is given in upssched.conf on the line starting CMDSCRIPT. This file probably doesn’t exist – so just create a new one. Assuming it doesn’t exist add the following lines:
#! /bin/sh
case $1 in
powersave)
/usr/bin/cpufreq-selector --governor powersave && logger -t upssched-cmd "Setting CPU Governor to powersave"
;;
userspace)
/usr/bin/cpufreq-selector --governor userspace && logger -t upssched-cmd "Setting CPU Governor to userspace"
;;
*)
logger -t upssched-cmd "Unrecognized command: $1"
;;
esac

• Test Unplug you’re UPS for 1 min, plug back in and look at /var/log/syslog – you should see that NUTs has throttled you’re CPU.

I haven’t had a power cut since I’ve implemented this, but from looking at the stats from the UPS I should gain another 7 min or so of battery time – an extra 21%. An improvement on this may be stopping some process and task when on battery and starting them again when back on mains. But for now, at least untill the next power cut this will do for me.

[WUFTPD]
# Option: enabled
# Notes.: enable monitoring for this section.
# Values: [true | false] Default: true
#
enabled = true

# Option: logfile
# Notes.: logfile to monitor.
# Values: FILE Default: /var/log/auth.log
#
logfile = /var/log/auth.log

# Option: port
# Notes.: specifies port to monitor
# Values: [ NUM | STRING ] Default:
#
port = ftp

# Option: timeregex
# Notes.: regex to match timestamp in SSH logfile. For TAI64N format,
# use timeregex = @[0-9a-f]{24}
# Values: [Mar 7 17:53:28]
# Default: \S{3}\s{1,2}\d{1,2} \d{2}:\d{2}:\d{2}
#
timeregex = \S{3}\s{1,2}\d{1,2} \d{2}:\d{2}:\d{2}

# Option: timepattern
# Notes.: format used in "timeregex" fields definition. Note that '%' must be
# escaped with '%' (see http://rgruet.free.fr/PQR2.3.html#timeModule).
# For TAI64N format, use timepattern = tai64n
# Values: TEXT Default: %%b %%d %%H:%%M:%%S
#
timepattern = %%b %%d %%H:%%M:%%S

# Option: failregex
# Notes.: regex to match the password failures messages in the logfile.
# Values: TEXT Default: (?:Authentication failure|Failed (?:keyboard-interactive/pam|password)) for(?: illegal user)? .* from (?:::f{4,6}:)?(?P\S*)
failregex = wu-ftpd\[\d+\]:\s+\(pam_unix\)\s+authentication failure.* rhost=(?P<host>\S*)

To add it back add the following line to /etc/vim/gvimrc

" Also switch on highlighting the last used search pattern.
if has("syntax") && (&t_Co > 2 || has("gui_running"))
syntax on
set hlsearch
endif