Free iowa state software for linux

StateML is a State Machine Markup Language, with GraphViz and template-driven code generation.

SYNOPSIS

## See the stml command for command line use (recommended)

## Heres what a .stml file might look like:

< machine
id="main"
xmlns="http://slaysys.com/StateML/1.0"
xmlns:C="http://your.com/path/to/ns/for/C/code"
xmlns:Perl="http://your.com/path/to/ns/for/perl/code"
xmlns:Java="http://your.com/path/to/ns/for/Java/code"
...
>
< event id="init">
< C:api>void init_event_handler()< /C:api>
< /event>
< state id="#ALL" graphviz:style="dashed">
< arc event_id="init" goto="running">
< C:handler>init_device()< /C:handler>
< /arc>
< /state>
< state id="running"/>
< /machine>

use StateML;

my $machine = StateML->parse( $source ); ## filename, GLOB, etc.

StateML->parse( $source, $machine ); ## Add to existing machine

... process $machine as needed, see stml source for ideas...

WARNING: Alpha code. I use it in production, but you may want to limit your use to development only.

StateML is an XML dialect and a tool (stml) that reads this dialect (by default from files with a ".stml" extension) and converts it to source code using source code to a data structure.

It can then emit the data structure as a graphviz-generated image or graph specification or you may take the data structure and do what you want with it (bin/stml can pass it to template toolkit, for instance).
parse

my $m = StateML->parse( $StateML_string ) ;
my $m = StateML->parse( *F ) ;

multistat is a generic program to display the up/down status of all kinds of things (some examples: VPN, particular machines, whether filesystems are mounted).

You will need to edit the multistat.py file to configure the things whose status you want to check.

Status for each "property" (i.e., VPN, computer, filesystem mount) is either red or green.

For each property, you enter values into several arrays, as defined below

Taken from multistat.py:

# commands that set properties to the green state
green_cmds = []

# commands that set properties to the red state
red_cmds = []

# commands whose output can be used to determine whether the state is green or red
check_colour_cmds = []

# strings that, if present in check_colour_cmds, mean that we are in the green state
is_green = []

# display this when in the green state
green_display_strings = []

# display this when in the red state
red_display_strings = []

So what happens is:

For each property:

1. In the green state the green_display_strings value for the property is displayed in green.

2. In the red state the red_display_strings value for the property is displayed in red.

3. To determine whether the property is in the gren or red state, the command in the check_colour_cmds array is run, and if the string in the is_green array is found in the output, then the property is in the green state. Otherwise, it is in the red state.

4. If green_cmds and red_cmds are not null (they MUST be defined, but they MAY be empty strings), then clicking the displayed string for the property on the widget will cause the relevant command to be executed to cause the property to change state. In other words, you can force a property to toggle between green and red by clicking the property on the widget. So, for example, you can mount/umount filesystems with a click. For some properties it makes no sense to provide a toggle (for example, if you are simply monitoring whether a particular computer is on the network): for such properties, define red_cmds and green_cmds to be empty strings.

This may not make much sense (sorry!) but if you read it again with the multistat.py script open in front of you, you should be able to see what I mean.

You can change the actual displayed colours easily (see screenshot 2 for an example where "red" has been redefined).

By default, properties are scanned and updated once per miute.

libmysqltemplate project is a very high speed C state machine template library that uses MySQL data for the source of the templates and optionally for name/value pairs.

It is required for the mysqlApache2/mysqlMail2/iDNS family of openisp.net/unixservice.com Web based consoles for clusters and other complex Internet service infrastructure management.

State Threads project is a small library for designing scalable Internet applications.
The State Threads is a small application library which provides a foundation for writing fast and highly scalable Internet applications (such as Web servers, proxy servers, mail transfer agents, etc.) on UNIX-like platforms.
It offers a threading API for structuring a network application as an event-driven state machine.
The State Threads library is a derivative of the Netscape Portable Runtime library (NSPR) and therefore is distributed under the Mozilla Public License (MPL) version 1.1 or the GNU General Public License (GPL) version 2 or later.
Enhancements:
- Added support for kqueue and epoll on platforms that support them.
- Added ability to choose the event notification system at program startup.
- Long-overdue public definitions of ST_UTIME_NO_TIMEOUT (-1ULL) and ST_UTIME_NO_WAIT (0) [bug 1514436].
- Documentation patch for st_utime() [bug 1514484].
- Documentation patch for st_timecache_set() [bug 1514486].
- Documentation patch for st_netfd_serialize_accept() [bug 1514494].
- Added st_writev_resid() [rfe 1538344].
- Added st_readv_resid() [rfe 1538768] and, for symmetry, st_readv().

TorK project is a Tor Controller for KDE.

TorK allows you to configure, run and update Tor. It also allows you to view the Tor network and choose how you would like to interact with the network.

TorK is very much in an alpha state.

Concurrent Hierarchical State Machine (CHSM) is a language system for specifying concurrent, hierarchical, finite state machines (an implementation of "statecharts") to model and control reactive systems.
CHSM uses its own statechart specification langauge annotated with either C++ or Java code fragments in the tradition of yacc grammars with C code fragments. The generated code is fully object oriented allowing multiple state machines to exist concurrently. The CHSM run-time library is small, efficient, and thread-safe.
CHSM has been used successfullly in production environments such as CERN, Philips, and Qualcomm. There is an independent review from users at CERN.
Enhancements:
- The "dominance" rule has been extended from parent/child transitions to sibling transitions.
- This allows "if-else" transitions to be done more efficiently.