Free mrtg mica probe 0.0.2 software for linux

mrtg-mica-probe is a Telebit MicaBlazer modem usage probe.
mrtg-mica-probe is a modem usage probe for the ITK NetBlazer 6100 (formerly Telebit MicaBlazer) 3.32. It is used to monitor the number of used modem and ISDN lines.
The latest release of mrtg-mica-probe can always be found on the web at http://pwo.de/projects/mrtg/ or via anonymous ftp at ftp://ftp.pwo.de/pub/pwo/mrtg/mrtg-mica-probe/.
mrtg.cfg-mica shows some sample mrtg.cfg entries.
Enhancements:
- added documentation to workaround a Telebit bug that might prevent SNMP from starting correctly.

mrtg-ntap-probe can probe for Network Appliance NetCache caching appliance and NetApp Filer.

mrtg-ntap-probe retrieves the disk and file (inode) utilization by volume or quota tree name, so you do not need to find the right OID, which might change over time as you add and/or remove volumes and quota trees.

You need a recent release of mrtg 2.x, perl 5.003 or better, a NetApp NetCache appliance with NetCache release 5.1 or better and/or a Network Appliance Filer running Data Ontap 6.0 or better.

If you have a Network Appliance service contract and access to their software tools library on now.netapp.com, you should also take a look at their mrtg-filer and mrtg-netcache packages!

MRTG::Parse is a Perl extension for parsing and utilizing the logfiles generated by the famous MRTG Tool.

SYNOPSIS

use strict;
use MRTG::Parse;

my $mrtg_logfile = "/var/www/htdocs/mrtg/eth0.log";
my $period = "day";
my $desired_unit = "GB";

my ($traffic_incoming, $traffic_outgoing, $traffic_sum) = mrtg_parse($mrtg_logfile, $period, $desired_unit);

print "Incoming Traffic: $traffic_incomingn";
print "Outgoing Traffic: $traffic_outgoingn";
print "= Sum $traffic_sumn";

This perl extension enables its users to parse and utilize the logfiles that are generated by the famous MRTG (Multi Router Traffic Grapher) tool.

mrtg_parse() takes three argument:

1st: filename of the mrtg logfile
2nd: time period to genereate the output for
valid values are:
- individual time periods like: 20040821-20050130 (ISO 8601)
- static values: day, month, year
3rd: the desired unit (optional)
valid values are:
- B, KB, MB, GB, TB
- if missing mrtg_parse will chose an adequate one for you
mrtg_parse() returns three values:

1st: Incoming traffic
2nd: Outgoing traffic
3rd: Sum of incoming and outgoing

Kxremote is an application to integrate protocols of remote connection made with perlqt.
Supports:
- xdmcp
- vnc
- rdp

Warehouse project is a shoving boxes game.

Warehouse is a puzzle/strategy game that involves shoving boxes around a crowded warehouse.

It is loosly based off of the classic "Shove It" game for the SEGA Genisis (Actually much of the current level design is from my memories of playing that game).

THC-Probe is the ultimate host scanner compilation for Linux, featuring nmap, snmpscan, netbios auditing tool and super-cool vh shell script.

INSTALL: just run "make install". Everything will be installed in /usr/local

RUN: just run "netprobe" and see the options.

Every host scanned will be saved as a "host.bla.com.probe" file in your current directory.

It does many stuff like snmp guessing, samba pw guessing and information gathering.

Nothing great and big, but it suits my needs.

MRTG::Config is a Perl module for parsing MRTG configuration files.

WARNING

This module, while reliable right now, is still in ALPHA stages of development... The API/methods may change. Behaviors of methods will almost certainly change. The internal structure of data will change, as will many other things.

I will try to always release working versions, but anyone who expects their code that uses this module to continue working shouldnt... until I remove this warning.

SYNOPSIS

Ever have the need to parse an MRTG config file? I have. I needed to parse lots and lots of them. Using the functions built-in to MRTG_lib was too slow, too complex, and used too much RAM and CPU time for my poor web server to handle - and the data structures MRTG_lib built were way more complex than I needed.

MRTG::Config can load and parse MRTG and MRTG-style confiuguration files very quickly, and the parsed directives, targets and values can be located, extracted, and manipulated through an OO interface.

This module is intended to focus on correctly parsing the format of an MRTG configuration, regardless of whether or not the directives and values, etc. are valid for MRTG. I am using both the parsing behavior of MRTG_libs readcfg() function and the description of the format on the MRTG website as my guidelines on how to correctly parse these configuration files. I am still a short way off that goal, but this module is currently being used in a production environment with great success!

PLEA FOR MERCY

I plan on adding to this documentation and making it better organized soon, but Im willing to answer questions directly in the mean time. Also, this is my first module, written in a hurry to appease some disgruntled engineers. I do plan on continuing to improve it, so any input, positive or negative is certainly welcome!

USAGE EXAMPLE

use MRTG::Config;

my $cfgFile = mrtg.cfg;
my $persist_file = mrtg.cfg.db;

my $mrtgCfg = new MRTG::Config;

$mrtgCfg->loadparse($cfgFile);

# Want to store the parsed data for use later or by
# another program?
$mrtgCfg->persist_file($persist_file);
$mrtgCfg->persist(1);

foreach my $tgtName (@{$mrtgCfg->targets()}) {
my $tgtCfg = $mrtgCfg->target($tgtName);
# Lets assume every target has a Title.
print $tgtCfg->{title} . "n";
}

# globals() has some, um, interesting things you
# should know. Please read about it below...
my $globalCfg = $mrtgCfg->globals();

# Lets assume WorkDir is set.
print $globalCfg->{workdir} . "n";

ghli is GPMIs Highlevel Language Interpreter, developed to operate under GPMI, though it works as a standalone script interpreter as well.

It features a byte code interpreter with complex instructions for high level languages, a framework to ease implementing precompilers, a Pascal precompiler, and an Assembly precompiler.

It aims to be small, fast, and flexible. The number of core instructions are very limited while it offers a simple interface so the host application can register its own extension commands easily.