Free to collect software for linux

It is a package useful to collect statistics from remote nodes. That includes standard server metrics and any other numerical quantity we can use to characterize the node state (as the number of users or processes).

It is built under a distributed agent-manager model. RRDtool is used as database, so representation capabilities are bundled.

Although rrdUtils are not a requisite, they are used in some auxiliar tasks and using both tools is highly recommended.

Installation:

Manager side

gunzip -c rrdUtils-3.1.tar.gz | tar -xf -
cd rrdUtils
./configure --with-rrddir=/stats
make install

gunzip -c stats-station-3.0.tar.gz | tar -xf -
cd stats-station
./configure --with-statsdir=/stats --with-port=666
make install

cd rrdConf
./install_confs.sh
./haz_index.sh -g

The -g flag creates graphs with the html pages, and reduces the number of error messages that haz_index will issue.
The only task that needs to be completed at this point is the periodic graphs generation by a crontab entry that calls the make_graphs.sh script.
Once we start the server using the provided initscript, we get the manager side ready.

Agent side

gunzip -c stats-3.0.tar.gz | tar -xf -
cd stats
./configure --with-host=central.node --with-port=666
--with-statsdir=/usr/local/stats
make install

With a crontab entry to execute the statlaunch script every 15 minutes, the whole system is up and running.

CDCollect is a CD catalog application for gnome 2.8. Its functionality is similar to the old gtktalog application for gnome 1.4.
CDCollects goal is to be able to catalog your entire CD collection allowing for searches of your CD files with a clean and simple interface.
CDCollect is written in mono using monodevelop and the gtk-sharp and sqlite libraries.
Main features:
- Easy to use interface (if you feel it does not follow the gnome hig then its a bug).
- Allow the use of plugins (external programs) to collect information for each file of a CD in your catalog.
- Searches can be performed on CDs or files in the collection.
- It also catalogs compressed files (using external programs such as unzip, unrar, etc.).

DB based NetFLow Collector aims to collect Cisco NetFlow data and store it to a database.
DB based NetFlow Collector has a plugin interface, which makes it flexible for fitting in particular tasks.
Enhancements:
- First release. post your comments/bug reports.

HPCToolkit is an open-source suite of multi-platform tools for profile-based performance analysis of applications. The figure provides an overview of the toolkit components and their relationships.
Main features:
- hpcrun: a tool for profiling executions of unmodified application binaries using statistical sampling of hardware performance counters.
- hpcprof & xprof: tools for interpeting sample-based execution profiles and relating them back to program source lines.
- bloop: a tool for analyzing application binaries to recover program structure; namely, to identify where loops are present and what program source lines they contain.
- hpcview: a tool for correlating program structure information, multiple sample-based performance profiles, and program source code to produce a performance database.
- hpcviewer: a java-based GUI for exploring databases consisting of performance information correlated with program source.
A program called hpcview is at the toolkits center. It takes performance profiles, program structure information, and, under the direction of a configuration file, correlates it with application source code to produce a browsable performance database.
hpcview also enables the user to define expressions to compute derived metrics as functions other metrics already defined (e.g. measured metrics read from data files or previously-computed derived metrics).
Performance databases are explored using our Java-based hpcviewer user interface that enables one to explore an applications performance data in a top-down fashion and enables one to easily navigate back and forth between performance data and source code.
The user interface presents performance data in a hierarchical display. At any time, you are looking at some program context (program, file, procedure, loop, or line). Also displayed is the data for both the parent and the children of the current context. Up and down arrows on the lines of the display are used to walk the hierarchy.
In order to speed up top-down analysis, the interface also provides `flatten and `un-flatten buttons. Their icons hint at their function. `Flatten modifies the hierarchy by eliding non-leaf children of the current node and replacing them with the grandchildren.
Unflatten reverses this. Since the tables are sorted, the flatten operation makes short work of diving into the program from the top to identify the most important files, procedures, loops and statements.
Performance data manipulated by hpcview can come from any source, as long as the profile data can be translated or saved directly to a standard, profile-like input format. To date, the principal sources of input data for hpcview have been hardware performance counter profiles.
Such profiles are generated by setting up a hardware counter to monitor events of interest (e.g., primary cache misses), to generate a trap when the counter overflows, and then to histogram the program counter values at which these traps occur. For Linux, we developed the hpcrun tool to collect profiles by sampling hardware performance counters.
This tool uses UTKs PAPI library for access to hardware performance counters. A second tool, hpcprof is used to map profiles collected using hpcrun back to program source lines. hpcprof is based on code from Curt Janssens cprof/vprof profiler. On operating systems other than Linux, we use vendor-supplied tools to collect profile data. On MIPS+Irix platforms, we use SGIs ssrun tool to collect profiles. On Alpha+Tru64, we use either with Compaqs uprofile or DCPI utilities for this purpose.
hpcview and hpcviewer can be used to view profile-like data of any type, not just data sampled from hardware performance counters. To analyze one program that contained many register spills, we built a perl script to examine assembly code generated by the SGI compilers for MIPS+Irix and create profiles that map register spills back to source code lines.
To facilitate automation, the programs in HPCToolkit are intended to be run using scripts and configuration files. Once these are set up, rerunning the program to collect new data, and all of the steps that go into generating a browsable dataset can be completely automated. The scripts automate the collection of data and conversion of profile data into a common, XML-based format.
Other performance tools (e.g. SGIs ssrun) report performance data at the line, procedure, and program level. However, since much of the time in scientific programs is spent in loops; having data at the loop level as well is critical to facilitate performance tuning.
For this reason, HPCToolkit includes a binary analyzer bloop that extracts loop nesting structure from application binaries and uses symbol table line map information to map this structure back to the source programs level. Because bloop works on binaries, this process is independent of the language used (though in practice it can be somewhat compiler dependent).
The loop nesting structure information produced by bloop enables hpcview to associate performance data with each loop in a program without incurring any additional overhead for data collection during program execution.
Supported platforms: Pentium+Linux, Opteron+Linux, Athlon+Linux, Itanium+Linux, Alpha+Tru64 and MIPS+Irix.
HPCToolkit is open-source software released with a BSD-like license.

genlogstatcoll is a generic collector to collect statistic data from log file delivered in via a syslog interface and provided via the AgentX interface through a SNMP daemon.

A syslog daemon (for instance syslog-ng) has to be configured to send relevant data (for instance the messages on the facility MAIL) to the genlogstatcoll too.

Considering the genlogstatcoll input interface is configured on 172.16.1.12, port 9514, this config line for syslog-ng will do the trick:

destination maillog { file("/var/log/mail/$YEAR/$MONTH/$DAY/mail.log"
create_dirs(yes) dir_perm(0755) owner("root") group("mail")
perm(0640)); udp("172.16.1.12" port(9514)); };

An SNMP daemon (for instance net-snmp 5.2.3) has to be configured to open the AgentX interface.

Considering the SNMP daemon should open the interface on 172.16.1.12, port 9161, these line in the snmpd.conf will do it:

master agentx
AgentXSocket 172.16.1.12:9161

Now, you can configure a facility to filter the input data, a SNMP oid to mount on and a couple of regexes, to count their matches in the log data.

No Friction is a roll-a-ball-and-collect-the-dots puzzle game.

In this simple puzzle game, you control a rolling ball that has to collect the green dots and make it to the end of each level.

The ball can only be sent rolling if its sitting still, and it only stops when it hits a wall; it cant change direction once its moving.

It sounds simple, but there are 20 progressively harder levels - only a master can beat them all, and piece together the code that reveals the solution to Level X.
There is also a secret level, and the entrance is hidden underneath a breakable block somewhere in the game.

Keys:

Enter: Restart current level
F: Toggle fullscreen mode
F2: Return to the selection screen
F3: Save what level youre currently on
F4: Load a level youve previously saved

Tellu computer inspector collects hardware and software information from large computer client networks, and stores data in MySQL database.
Tellu package is divided into three sub-packages: Client, Server and Skin. Client and server packages are essential for Tellu to work. Client program collects the actual information from network, and sends them to the server which saves the data in local or remote MySQL database.
Skin is an optional interface top of that database, but to get fun out of Tellu, it is recommended to install. Server package also contains a monitoring server, which collects information about Tellu server. There is a Motif based client for monitoring server activity, which uses monitoring server to read actual activity data.
Enhancements:
- Support for a compressed protocol was added in the client and the server.
- A rush tolerance option was added, which delays the client from starting more than once within fifteen seconds.
- A process count in realtime resource usage collection was added.
- The capability to collect new hardware items was added in client.
- An attachment browser was added in the skin, and some other improvements were made in the skin.

Thinking Rock project is a Java based software application for collecting and processing your thoughts, following the GTD methodology.
Thinking Rock allows you to collect your thoughts and process them into actions, projects, information or future possibilities. Actions can be done by you, delegated to someone else or scheduled for a particular date. Projects can be organised with ordered actions and sub-projects. You can review all of your actions, projects and other information quickly and easily to see what you need to do or to choose what you want to do at a particular time.
Main features:
- It will help you to store in one safe place all the things you have to do or would like to do one day;
- Unlike many task management applications, Thinking Rock lets you to group your actions in projects and sub-projects;
- It gets you moving on your thoughts by encouraging you to think of the next physical action to take;
- It is simple, easy (help documentation provided) and quick to use ;
- We provide free customer support;
- The data file is separate so you can have the application installed on your home computer and at work, and transfer the small data file between computers;
- It is multi-platform: use it on Linux, Machintosh, or Windows;
- Its free.