Free nerolinux 3 software for linux

Fcron project is a periodical command scheduler which aims at replacing Vixie Cron, so it implements most of its functionalities.
But fcron does not assume that your system is running neither all the time nor regularly : you can, for instance, tell fcron to execute tasks every x hours y minutes of system up time or to do a job only once in a specified interval of time.
Fcron has also much more functionalities : you can also set a nice value to a job, run it depending on the system load average and much more !
Enhancements:
- Since 3.0.2, the build and install processes have changed significantly to make them more standard and make fcron easier to package, and AIX and Solaris platforms are supported better.
- Some other minor changes give better compatibility with Vixie cron.
- Please bear in mind that the default install paths have changed since 3.0.3-rc1 to make them more standard.

Munin is a tool for graphing all sorts of information about one or more servers and displaying it in a web interface. Munin uses the execellent RRDTool (written by Tobi Oetiker) and is written in Perl. Munin has a master/node architecture.
The master connects to all the nodes at regular intervals, and asks them for data. It then stores the data in RRD-files, and (if needed) updates the graphs. One of the main goals has been ease of creating own "plugins" (graphs).
Installation:
edit Makefile.config
- create the user "munin"
- make install-main
- create a cron-entry to run "munin-cron" as the user "munin" every 5 minutes
- if you want to use the dynamic graphs, configure the cgi directory (an example for apache can be found in README-apache-cgi).

LinCAN is a Linux kernel module that implements a CAN driver capable of working with multiple cards, even with different chips and IO methods. Each communication object can be accessed from multiple applications concurrently.
It supports RT-Linux, 2.2, 2.4, and 2.6 with fully implemented select, poll, fasync, O_NONBLOCK, and O_SYNC semantics and multithreaded read/write capabilities. It works with the common Intel i82527, Philips 82c200, and Philips SJA1000 (in standard and PeliCAN mode) CAN controllers.
LinCAN project is part of a set of CAN/CANopen related components developed as part of OCERA framework.
Enhancements:
- Some more fixes were made in SJA1000 bus-off recovery.
- The i82527 IRQ stuck problem was fixed.
- The module was updated and tested up to kernel version 2.6.17 (rc4).
- Minimal chip information was added in /proc/can.
- Support for NSI CAN PCI was contributed.

shntool is a multi-purpose WAVE data processing and reporting utility. File formats are abstracted from its core, so it can process any file that contains WAVE data, compressed or not - provided there exists a format module to handle that particular file type. shntool is comprised of three parts: the core, mode modules, and format modules.
shntool has native support for .wav files. If you want it to work with other formats, you must have the appropriate helper program installed. The "Helper programs" section below contains links to helper programs for each format that shntool supports.
Enhancements:
- This version improves the use of exit codes across all modes.

ddclient is a client for updating dynamic DNS entries for accounts on a number of dynamic DNS providers, including Dynamic DNS Network Services free DNS service.
Many different routers are supported.
ddclient is a small but full featured client requiring only Perl and no additional modules. ddclient project runs under most UNIX OSes and has been tested under GNU/Linux and FreeBSD.
Main features:
- operating as a daemon
- manual and automatic updates
- static and dynamic updates
- optimized updates for multiple addresses
- MX
- wildcards
- abuse avoidance
- retrying failed updates
- sending update status to syslog and through e-mail.

Valgrind is an award-winning suite of tools for debugging and profiling Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs.
Valgrind distribution currently includes three tools: a memory error detectors, a cache (time) profiler and a heap (space) profiler.
Valgrind is Open Source / Free Software, and is freely available under the GNU General Public License.
Main features:
- Valgrind will save you hours of debugging time. With Valgrind tools you can automatically detect many memory management and threading bugs. This gives you confidence that your programs are free of many common bugs, some of which would take hours to find manually, or never be found at all. You can find and eliminate bugs before they become a problem.
- Valgrind can help you speed up your programs. With Valgrind tools you can also perform very detailed profiling to help speed up your programs.
- Valgrind is free. Free-as-in-speech: you can download it, read the source code, make modifications, and pass them on, all within the limits of the GNU GPL. And free-as-in-beer: we arent charging for it.
- Valgrind runs on x86/Linux, AMD64/Linux and PPC32/Linux, several of the most popular platforms in use. Valgrind works with all the major Linux distributions, including Red Hat, SuSE, Debian, Gentoo, Slackware, Mandrake, etc.
- Valgrind is easy to use. Valgrind uses dynamic binary translation, so you dont need to modify, recompile or relink your applications. Just prefix your command line with valgrind and everything works.
- Valgrind is not a toy. Valgrind is first and foremost a debugging and profiling system for large, complex programs. We have had feedback from users working on projects with up to 25 million lines of code. It has been used on projects of all sizes, from single-user personal projects, to projects with hundreds of programmers.
- Valgrind is suitable for any type of software. Valgrind has been used on almost every kind of software imaginable: desktop applications, libraries, databases, games, web browsers, network servers, distributed control systems, virtual reality frameworks, transaction servers, compilers, interpreters, virtual machines, telecom applications, embedded software, medical imaging, scientific programming, signal processing, video/audio programs, NASA Mars lander vision and rover navigation systems, business intelligence software, financial/banking software, operating system daemons, etc, etc. See a list of projects using Valgrind.
- Valgrind is widely used. Valgrind has been used by thousands of programmers across the world. We have received feedback from users in over 25 countries, including: Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Italy, The Netherlands, Norway, Poland, Portugal, Russia, Sweden, Switzerland, UK, Argentina, Brazil, Canada, USA, Australia, India, Japan, New Zealand, Singapore, South Africa and Israel.
- Valgrind works with programs written in any language. Because Valgrind works directly with program binaries, it works with programs written in any programming language, be they compiled, just-in-time compiled, or interpreted. The Valgrind tools are largely aimed at programs written in C and C++, because programs written in these languages tend to have the most bugs! But it can, for example, be used to debug and profile systems written in a mixture of languages. Valgrind has been used on programs written partly or entirely in C, C++, Java, Perl, Python, assembly code, Fortran, Ada, and many others.
- Valgrind debugs and profiles your entire program. Unlike tools that require a recompilation step, Valgrind gives you total debugging and profiling coverage of every instruction executed by your program, even within system libraries. You can even use Valgrind on programs for which you dont have the source code.
- Valgrind can be used with other tools. Valgrind can start GDB and attach it to your program at the point(s) where errors are detected, so that you can poke around and figure out what was going on at the time.
- Valgrind is extensible. Valgrind consists of the Valgrind core, which provides a synthetic software CPU, and Valgrind tools, which plug into the core, and instrument and analyse the running program. Anyone can write powerful new tools that add arbitrary instrumentation to programs. This is much easier than writing such tools from scratch. This makes Valgrind ideal for experimenting with new kinds of debuggers, profilers, and similar tools.
- Valgrind is actively maintained. The Valgrind developers are constantly working to fix bugs, improve Valgrind, and ensure it works as new Linux distributions and libraries come out. There are also mailing lists you can subscribe to, and contact if youre having problems.
- So whats the catch? The main one is that programs run significantly more slowly under Valgrind. Depending on which tool you use, the slowdown factor can range from 5--100. This slowdown is similar to that of similar debugging and profiling tools. But since you dont have to use Valgrind all the time, this usually isnt too much of a problem. The hours youll save debugging will more than make up for it.
Enhancements:
- 3.2.3 is almost identical to 3.2.2, but fixes a regression that unfortunately crept into 3.2.2. The regression causes an assertion failure in Valgrind when running certain obscure SSE code fragments on x86-linux and amd64-linux. Please do not use (or package) 3.2.2; instead use 3.2.3.