The aforementioned site work is complete. Not really all that thrilling. Following are some of the chores wrapped up:
Last year I put together a book with selected texts from the site and some
new material. The topic is basically the same as most of the site content
regarding programming. After peddling the draft around I finally decided
I didn't have the energy to keep packaging it up along with supporting
materials anymore. Instead I decided to just give it away under a
Creative Commons license. If there is any interest in the book (and that is a
big if) I might do another one packaging up all of the site material as
a sort of reference/history. The working title is simply System
Utility Programming
and can be perused in a variety of formats:
All of itDownloads
sourcetext files
Additionally I broke it up into the major sections:
Part 0 · Part 1 · Part 2 · Part A
The cover
can be found here for those who might want to print
out the entire book.
netreconn AvailableI have branched a new version of the netreconn tools. There
have been some major changes to it and there is still a lot of work yet to
go. Following is a list of major changes:
Here are a few of the TODOs. As per the norm some, none, all or totally different things may happen to the utilities:
scanlan TODOswiretraf TODOsThe git repo has all updated sources
now for netreconn as well.
Dnet WorkIn addition to all of the other stuff I have been up to
lately I managed to find time to wrap up a small Nmap
project and complete (at least as far as my infrastructure
supports it) a big chunk of Dnet work.
std::map for payload
lookups. What does this mean? If one wishes to use a new payload
all they have to do is add it to nmap-payloads versus
adding it to the code and recompiling. Currently only
UDP is supported.Of course expect this entry to be deleted soon. Over the next month I might be taking a break from writing to perform some content maintenance. This is what happens when one does not use a database. They have to clean stuff. Specifically the news needs compressed into simple lists (which has to be done manually... great). Also the texts index page needs some new series lists put together and in of itself might need to be split (I haven't really decided yet). No fear, I do have some interesting content on the horizon (in the form of notes) I just need to sit down and actually, you know, write it. I think the about section could use a punch in the arm as well but we shall see. I do not plan on changing the design, just content whereabouts, lists and so forth. Honestly the design took me so long to settle on and is so complex at this point, I am kind of scared of even looking at it.
In part one of this series the basic trusses needed by the Nagios check_systemhealth script were put together. In part two the actual checks themselves were coded. In this the third and final part of the series compulsory checks are added, the main loop is constructed and the final full source listing produced.
It is worth noting that this is only one of many methods to achieve the same goal. There exists at Nagios exchange plugins and scripts that can do similar actions such as aggregate groups of checks, services and so on. The code presented in this series is just a touch upon a single idea designed to make the reader think about their monitoring deployment.
Yes I posted this today to avoid the April Fool's joke wonderings.
Recently during a short period of severe boredom I decided to try and
change my habits a bit by using - when possible - nothing but command
line tools. I did allow for the use of curses based tools too, so I guess
console or terminal only tools would be a more appropiate way to state the
experiment.
Many of the tools I already did use but I wanted to see
if I could use exclusively console commands/tools/utils for a week or so.
The result was pretty surprising, excepting Firefox (which I found a retro
skin theme for) and audacious (for streaming internet music stations) I
still use nothing but console utilities in my Xsession and am still using
the window manager I setup. Note this is not a review of tools or anything
like that, just an experiment that had some unexpected benefits. I am
thinking about trying the opposite but I fear it won't be nearly
as interesting.
Fixa Problem
Ever had an ipv4 network address that is supposed to migrate over via a high availability mechanism simply not work or even stranger if there were several addresses some do and some do not? An experienced network administrator probably has seen mysterious non-migrating addresses, however, within this context is presented a rather interesting "solution" to when it has been observed.
netreconn-1.76
& mmw-2.0
Finally got around to releasing
the stable version of the
netreconn utilities. These are basically the same as 1.75 without any
changes. I think I am going to stop using the odd numbered/even numbered
method since there do not seem to be enough changes in between to bother.
I was really bored one day and finally did some work on
the micro memory watcher or mmw. The mmw utility is
basically a nicely formatted version of free. Following are
the changes in this version:
nettest 2.4 Updatenetreconn 1.75 Releasenettest 2.3 UpdateMeta Check1
libpcap Inettest to
2.1ip_conntrack_max Threshold Scriptpwutils
Packageretval Is Importantwish.