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).

Its now running on Debian for the next Cacti box (assuming it doesn’t have the gd bug).

What has helped with the new Cacti box is a combination of a few things - the new 1 min poller patch spreads I/O out better, and allows me to poll device which don’t do 64bit SNMP counters yet have gigabit ethernet ports every min, and leave everything else at 5 min. Improvements on plugins and a switch to cactid (a c version of the poller) has also really helped. The system now process ~400 hots in 35 seconds, dealing with ~4100 data sources and ~2200 rrd each min. Not bad.

There are a couple things that need improving however:
1) The threshold system now inspects data straight from the db before writing to the rrd files, which unfortunately causes the graphs in the email to be 1 cycle out of date (ie not show the data the emails about).
2) The Uptime+Threshold system host down email only works by patching files yourself at present when using cactid

As for ubuntu - either stop shipping cactid, or compile it again the correct version of the libraries. I’d much rather the package not be there than for it to not work, it gives people a bad impression.

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.

Well I’ve done something about it (well at least on my blog) - I’ve changed my theme so that on browsers the do css and media types the sidebar shouldn’t print out. Here’s how you can add this to you’re WordPress blog

1. Create a file print-style.css in the directory for you’re current theme with the following content
   .dontprint{ display: none; }
div#menu{ display: none; }
2. In wordpress, goto Presentation, Theme Editor and select the file Header
3. Just bellow the line setting the css style sheet - should be something like this :
   <style type="text/css" media="screen">
@import url( %lt;?php bloginfo('stylesheet_url'); ?> );
<style>

   add the lines
   <style type="text/css" media="print">
@import url(<?php bloginfo('template_directory'); ?>/style-print.css);
</style>
4. Hopefully this should be enough, but if the theme author hasn’t used the div’s in the sidebar file you may have to add this line <div id="menu"> to the top of the file and this line </div> to the bottom of the file

Anyway I have a fix for this now - simply call mostwanted using these two lines of php:
$mostwanted = new MostWanted;
$mostwanted->mostwanted(7, 30, true);

in replace of

MostWanted::mostwanted(7, 30, true);


[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

Easy to fix - log on. Goto system > administration and set a default printer. Still you’d have though that when I only have one printer, and its the first printer I added it would be the default, by well default

The two tables moved are: snmp_counter64* and poller_output. Both these tables can afford to loose the data on restart - they hold data before it is moved into the rra and holds at most 5 mins worth of data (IE one cycle).

It also improves the situation if the server restarts as if data is left in the poller_output table it can push the the php poller over its memory limit and stop it working properly, so its a good idea to start with it empty.

Snmp_counter64 also needs emptying every now and again - as when you remove devices from cacti it does not get removed from here

The SQL code to achieve this is:

alter table cacti.snmp_counter64 engine=heap;
delete from cacti.poller_output;
ALTER TABLE cacti.poller_output MODIFY COLUMN output VARCHAR(255);
alter table cacti.poller_output engine=heap;


Warning
Some graphs may stop updating if the script used to generate data for the output more the 255 characters If you use MYSQL 5, then you can use something like VARCHAR(1024) instead.
This may cause data to be lost from the current run.

The server now copes pretty well. I haven’t tried anything new to it yet, but it generally appears to be working better then it has done for past couple of months. I would like to re do the disk structure, but for now this will do.

*This table is from a patch - most people won’t have this table.

Currently it has:
Hosts:354 Data-Sources:16943 RRDs Processed:8744

And has hit a limit with Disk i/o.

What I plan to do is: Move it onto a temp virtual server. Completely rebuild the old dell with two RAID 1 sets each on 2 disks - One for the RRA and one for the DB and see how it put up with that. The rebuild should help on the disk layout too - due to all the network changes and low disk space its likely the disk could have a few few frags.

If this doesn’t work and it still struggles, then I’ll use one of the various other spare dells (might have to be one without a raid card - so it’ll be software raid) and stick the database and possibly front end on it.

Once we have it stable again - I suppose I better look into a better way of coping with gigabit Ethernet cards in windows - currently we use the SnmpProxy2.pl hack - may just be a case of limiting it to Windows servers some how and not all 64bit Ethernet counters.