Rpm

As some people know, I previously " created" (mostly modified the check_swap plug-in to print RAM usage) check_ram in C. Now one of my problems for the past few months was putting the C plug-in as well as " supported" environment under the same hat. Today I had another look at the amount of available plug-ins in NagiosExchange. There are quite a few plug-ins available, but as I do have some experience with Python, I used the one written in Python. It was rather easy hacking in support for performance data into it, as the below shows. Someone else already posted a non-unified diff for performance data support, but that ain’t quite right according to the Nagios plug-in development guidelines.

Remember, I talked about building RPM’s on SLES10SP2 on ppc64 ? Well, turns out I was rather stupid .. and it was rather simple (don’t ask me why I didn’t think of that). I tried asking solar, I used Google (apparently with the wrong search parameters), nothing though. Not a clue. Today it bugged me again, so I used Google again. This time with " ppc64 suse rpmbuild", and guess what I saw within the preview of the second hit .. ...

Well, as we do have quite a few custom built RPM’s, I was searching for a new solution to manage the repo(s). Currently I do have a single repository per distribution. One thing one needs to know about createrepo (from createrepo), it doesn’t support this type of thing in the first place. So I had to come up with another way of doing it. First, I created a proper layout (much like the Debian Official Repository layout): ...

OK, so I skipped rebuilding a newer RPM version (for now) and I’m currently rebuilding anything that fit’s into app-dev according to IBM … The list reads like this: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 $ ls -al ~/app-dev autoconf-2.59-1.aix5.1.noarch.rpm automake-1.8.5-1.aix5.1.noarch.rpm binutils-2.14-3.aix5.1.ppc.rpm bison-1.875-3.aix5.1.ppc.rpm coreutils-5.2.1-2.aix5.1.ppc.rpm cpio-2.5-1.aix5.1.ppc.rpm diffutils-2.8.1-1.aix4.3.ppc.rpm flex-2.5.4a-6.aix4.3.ppc.rpm gawk-3.1.3-1.aix5.1.ppc.rpm gcc-4.0.0-1.aix5.1.ppc.rpm gcc-cplusplus-4.0.0-1.aix5.1.ppc.rpm gdb-6.0-1.aix5.1.ppc.rpm libgcc-4.0.0-1.aix5.1.ppc.rpm libstdcplusplus-4.0.0-1.aix5.1.ppc.rpm libstdcplusplus-devel-4.0.0-1.aix5.1.ppc.rpm libtool-1.5.8-1.aix5.1.ppc.rpm m4-1.4.1-1.aix5.1.ppc.rpm make-3.80-1.aix5.1.ppc.rpm OK, I’m not exactly rebuilding these old versions, I’m actually using their old specs to compile newer versions of these. I’m currently at coreutils-6.7, which really takes ages. But will see about the rest. ...

OK, so today was the highlight of the week … We updated apache2 on Tuesday (yeah, that’s still 2.0.49, so if you have some exploits - try them 😛 ) and now out of the sudden we have major performance issues. We looked nearly the whole forenoon for a reason, why the frackin’ apache was using 236% of the CPU’s. In the afternoon, when my co-worker decided to go home (that was ~1500), I decided to revert back to the old patch level. But that isn’t as easy as you think (at least on SLES). The only thing I wanted to do, was something like this: ...

OK, so I tried to install the AIX Toolkit today, to build some newer rpm’s (yaaaaah, I hate RPMS myself, still it’s way better than distributing plain tar.gz archives) but looks like either AIX or rpm-4.4.7 doesn’t like me. Now I’ve to figure out how to get libm (that’s /lib/libm.so) installed on AIX. Will see about that later and/or tomorrow.

OK, so after yesterdays battle with SLES and rpm, I decided to simply upgrade rpm (again rpmbuild -bb rpm.spec as in from source). I had to tune (hah, remove stuff that isn’t working on this ancient gcc-3.3.3 ie. -fstack-protector) a bit to get it working, wasted 20 minutes worth of CPU time and ~30 of my time. I finally gave up. I couldn’t persuade neither rpm, nor git to compile on the damn SLES/Dell. ...