Free conditions software for linux

monit is a utility for managing and monitoring, processes, files, directories and devices on a UNIX system.
monit project conducts automatic maintenance and repair and can execute meaningful causal actions in error situations.
monit has monitored and mended computers around the world for over 4 years and is used on thousands of servers. Join the comunity today, download and install monit!
Monit can start a process if it does not run, restart a process if it does not respond and stop a process if it uses to much resources.
You can use monit to monitor files, directories and devices for changes, such as timestamp changes, checksum changes or size changes. You can also monitor remote hosts; monit can ping a remote host and can check TCP/IP port connections and server protocols.
Monit is controlled via an easy to use control file based on a free-format, token-oriented syntax. Monit logs to syslog or to its own log file and notifies you about error conditions and recovery status via customizable alert.
Enhancements:
- This is a feature and bugfix release.

con:cern project is a workflow engine based on an extended case handling approach.
A process is described as a set of activities with pre- and postconditions. An activity is executed when its preconditions are met. It manipulates the process item, thereby creating postconditions. The process flow is determined at runtime. This approach is superior to the conventional process flow approach, especially if high flexibility and modularity are required.
Main features:
- complex process with exceptions and special cases
- execution sequence is dependent on multiple factors
- possibility of manual intervention of process flow
- content-based dependence amongst activities
- strong requirements to modularity
- strong requirements to flexibility
- loose process coupling
Interestingly, processes often turn out to be more complex than initially anticipated. con:cerns flexibility allows to restrict yourself to implementing the normal process flow. Special cases and exceptions can be manually dealt with at run-time, or can be gradually retrofitted.
When you can break systems down to pre conditions, post conditions, transfer functions, and the algorithms that implement them you can go a long way towards reliable systems and specs.
Enhancements:
- bugfix escalation timeout
- bugfix reenlistment after escalation

Class::Contract - Design-by-Contract OO in Perl.

SYNOPSIS

package ClassName
use Class::Contract;

contract {
inherits BaseClass;

invar { ... };

attr data1;
attr data2 => HASH;

class attr shared => SCALAR;

ctor new;

method methodname;
pre { ... };
failmsg Error message;

post { ... };
failmsg Error message;

impl { ... };

method nextmethod;
impl { ... };

class method sharedmeth;
impl { ... };

# etc.
};

Background

Design-by-contract is a software engineering technique in which each module of a software system specifies explicitly what input (or data or arguments) it requires, and what output (or information or results) it guarantees to produce in response.

These specifications form the "clauses" of a contract between a module and the client software that uses it. If the client software abides by the input requirements, the module guarantees to produce the correct output. Hence by verifying these clauses at each interaction with a module, the overall behaviour of the system can be confidently predicted.
Design-by-contract reinforces the benefits of modular design techniques by inserting explicit compile-time or run-time checks on a contract. These checks are most often found in object-oriented languages and are typically implemented as pre-conditions and post-conditions on methods, and invariants on classes.

Note that these features differ from simple verification statements such as the C assert statement. Conditions and invariants are properties of a class, and are inherited by derived classes.

An additional capacity that is often provided in design-by-contract systems is the ability to selectively disable checking in production code. This allows the contractual testing to be carried out during implementation, without impinging on the performance of the final system.

Adding design-by-contract to Perl

The Class::Contract module provides a framework for specifying methods and attributes for a class (much like the existing class definition modules Class::Struct, Class::MethodMaker, and Class::Generate). Class::Contract allows both per-object and per-class methods and attributes to be defined. Attributes may be scalar-, array-, hash-, or object-based.

Class::Contract differs from other class-specification modules (except Class::Generate) in that it also provides the ability to specify invariant conditions on classes, and pre- and post-conditions on methods and attributes. All of these clauses are fully inheritable, and may be selectively disabled. It differs from all other modules in that it has a cleaner, simpler specification syntax, and -- more importantly -- it enforces encapsulation of object attributes, thereby ensuring that the class contract cannot be subverted.

Defining classes

Class::Contract provides an explicit syntax for defining the attributes, methods, and constructors of a class. The class itself is defined using the contract subroutine. contract takes a single argument -- a subroutine reference or a block. That block is executed once and the results used to construct and install the various components of the class in the current package:

package Queue;
contract {
# specification of class Queue attributes and methods here
};

SAM is a program to monitor (in real-time) the number of alerts generated by Snort. Having recently set up Snort and ACID I felt like there was something missing.

Snort was great for identifying suspicous traffic and ACID was great for digging in to the details but I needed something that was a little higher overview and able to sounds alarms if certain conditions were met.

For instance if I was attacked 100 times in a 5 minutes period. SAM does not replace Snort or ACID but rather it compliments them.

Multicast Dissemination Protocol project is a protocol framework and software toolkit for reliable multicasting data objects including files and application memory blocks. A primary design goal of MDP is to provide a reliable multicast protocol approach which is suitable for reliable dissemination of data over both wireless and wired networks.

MDP software has been demonstrated across a range of network architecture and heterogeneous conditions including; the worldwide Internet MBone, bandwidth and routing asymmetric network connections, high delay satellite networks, and mobile, radio networks. MDP integrates numerous multicast protocol advances including highly robust, packet-based erasure correction techniques and adaptive group timing mechanisms.

The present MDP software toolkit includes a library with a well-defined API. Several example working applications including a multicast file transfer applications and a very basic multicast chat application are also provided. To learn more and/or download the software see the following sections.

Quest OpenSSH provides password-less, secure, encrypted remote login and file transfer services for Vintela Authentication Services (VAS). It is a derivative of OpenSSH, an open-source implementation of the SSH protocol.
Quest OpenSSH provides:
- default single sign on for Quest customers using VAS or VMX. Users are automatically and securely authenticated against Microsoft Active Directory using GSSAPI.
- compatibility with other SSH tools, including Quest PuTTY.
- integrated enhancements including high performance network support and TCPwrap access controls.
The software packages include both the client, ssh, and the server, sshd. Packages are subject to open source licence conditions.
Enhancements:
- This releases new features are the Match directive and inclusion of the HPN patches (High Performance Networking).
- Minor bugs fixed include NIS+ compatibility and improved service script reliability.