Free delayed shutdown program software for linux

game control program project helps administrate game servers, especially automated kicking of players.
game control program helps you administrate gameservers (its written for Q1 and Q3, but works for others). It is highly modular and therefore extensible.
With the current modules, it can start/stop servers, create and rotate logfiles, allow remote administration via telnet, and kick misbehaving players automagically (according to a rule set).
Main features:
- starting a game server and getting hold of all log messages
- creating log files (complete or rotated per map)
- parsing log messages (game independent and configurable)
- sophisticated remote administration (user groups, extensible command set)
- sending commands to a running server (Q,QW,Q2,Q3)
- automatic kicking system according to specific rules (eg. too high rate set by the client)
- check if a server is hanging and kill the process to force a restart
- sending commands to the server at specified timesallows timed startup / shutdown of servers
Enhancements:
- renamed packages and modules (see doc/config)
- added new module: CommandScheduler
- sends a command to the server in defineable periods - see cfg/events.xml allows:
- COMMAND - send as RCon command (command is set as attribute parameter)
- KILLSERVER
- STARTUP
- SHUTDOWN

AIMLBot (Program#) is a small, fast, standards-compliant yet easily customizable .NET dll implementation of an AIML (Artificial Intelligence Markup Language) based chatter bot.
AIMLBot has been tested on both Microsofts runtime environment and Mono. Put simply, it will allow you to chat (by entering text) with your computer using natural language.
This is the second version of the library and it has been re-written from scratch.
Main features:
- Better cross-platform compatibility. Support for .NET 1.1, 2.0 and XNA as well as the open source Mono project (tested under version 1.1). Testing on Windows Vista with version 3.0 of the .NET platform is pending.
- A completely new modular architecture to make it easier for developers to extend and add functionality.
- A simpler and more logical API.
- Standards compliant AIML support with the option for custom tags.
- Very small size (currently only 52k).
- Very fast (over 30,000 categories processed in under a second).
- Inclusion of a comprehensive test suite including over 200 unit tests (based upon nUnit).
- A means of saving the bots "brain" as a binary file (Graphmaster.dat).
- Some simple code snippets and examples for developers to get started (simple windows and console based applications as well as a sample custom tags library).
- Appropriately commented code.
- Comprehensive documentation.
Enhancements:
- This version fixes a rather serious bug that crept into the last version where regex-based replacements caused the bot to either time out or produce incorrect paths for the graphmaster algorithm.
- In addition, generics are now used throughout, which will improve the performance of the bot.

Command Executor is an amaroK script which execute an internal command (e.g. stop playing) when reaches that entry. Sometimes it is useful to execute some external commands (e.g. shutdown) when playing reached a certain place (e.g. end of album).

This script does the job. If amaroK starts playing a track from the "Shell Command" album, this script executes the comment tag of the track as a shell command.

You need some prepared audio files, with correctly filled tags. There are three .ogg files enclosed for stop playing, shutdown and hibernate the computer.

Open Journal Systems (OJS) is a journal management and publishing system that has been developed by the Public Knowledge Project through its federally funded efforts to expand and improve access to research.
Main features:
- OJS is installed locally and locally controlled.
- Editors configure requirements, sections, review process, etc.
- Online submission and management of all content.
- Subscription module with delayed open access options.
- Comprehensive indexing of content part of global system.
- Reading Tools for content, based on field and editors choice.
- Email notification and commenting ability for readers.
- Complete context-sensitive online Help support.
OJS assists with every stage of the refereed publishing process, from submissions through to online publication and indexing. Through its management systems, its finely grained indexing of research, and the context it provides for research, OJS seeks to improve both the scholarly and public quality of referred research.
OJS is open source software made freely available to journals worldwide for the purpose of making open access publishing a viable option for more journals, as open access can increase a journals readership as well as its contribution to the public good on a global scale (see PKP Publications).

Class::Container is a Perl module with Glues object frameworks together transparently.

SYNOPSIS

package Car;
use Class::Container;
@ISA = qw(Class::Container);

__PACKAGE__->valid_params
(
paint => {default => burgundy},
style => {default => coupe},
windshield => {isa => Glass},
radio => {isa => Audio::Device},
);

__PACKAGE__->contained_objects
(
windshield => Glass::Shatterproof,
wheel => { class => Vehicle::Wheel,
delayed => 1 },
radio => Audio::MP3,
);

sub new {
my $package = shift;

# windshield and radio objects are created automatically by
# SUPER::new()
my $self = $package->SUPER::new(@_);

$self->{right_wheel} = $self->create_delayed_object(wheel);
... do any more initialization here ...
return $self;
}

This class facilitates building frameworks of several classes that inter-operate. It was first designed and built for HTML::Mason, in which the Compiler, Lexer, Interpreter, Resolver, Component, Buffer, and several other objects must create each other transparently, passing the appropriate parameters to the right class, possibly substituting other subclasses for any of these objects.

The main features of Class::Container are:

Explicit declaration of containment relationships (aggregation, factory creation, etc.)
Declaration of constructor parameters accepted by each member in a class framework
Transparent passing of constructor parameters to the class that needs them
Ability to create one (automatic) or many (manual) contained objects automatically and transparently

XFS combines advanced journaling technology with full 64-bit addressing and scalable structures and algorithms. This combination delivers the most scalable high-performance filesystem ever conceived.
Main features:
Quick Recovery
- The XFS journaling technology allows it to restart very quickly after an unexpected interruption, regardless of the number of files it is managing. Traditional filesystems must do special filesystem checks after an interruption, which can take many hours to complete. The XFS journaling avoids these lengthy filesystem checks.
Fast Transactions
- The XFS filesystem provides the advantages of journaling while minimizing the performance impact of journaling on read and write data transactions. Its journaling structures and algorithms are tuned to log the transactions rapidly.
- XFS uses efficient tree structures for fast searches and rapid space allocation. XFS continues to deliver rapid response times, even for directories with tens of thousands of entries.
Massive Scalability
- XFS is a full 64-bit filesystem, and thus is capable of handling filesystems as large as a million terabytes.
- 263 = 9 x 1018 = 9 exabytes
- A million terabytes is thousands of times larger than most large filesystems in use today. This may seem to be an extremely large address space, but it is needed to plan for the exponential disk density improvements observed in the storage industry in recent years. As disk capacity grows, not only does the address space need to be sufficiently large, but the structures and algorithms need to scale. XFS is ready today with the technologies needed for this scalability.
- XFS also continues to evolve to match the capabilities of the hardware it is being deployed on. Efficiency when dealing with large amounts (terabytes) of main memory and hence large numbers of active files and large amounts of cached file data are areas demanding continual improvements. Extending XFS to improve performance on large NUMA machines is also an area of active research and development.
Efficient Allocations
- XFS implements extremely sophisticated space management techniques. Efficiency in space management has been achieved through the use of variable sized extents, rather than the simple single-block-at-a-time mechanism of many other filesystems. XFS was the first filesystem to implement delayed space allocation for buffered writes, supports direct I/O, provides an optional realtime allocator, and is able to align allocations based on the geometry of the underlying storage device. The XFS allocator performs admirably in the presence of multiple parallel writers, and is renowned for its resistance to space fragmentation under such conditions.
Excellent Bandwidth
- XFS is capable of delivering very close to the raw I/O performance that the underlying hardware can provide. XFS has proven scalability on SGI Altix systems of multiple gigabytes-per-second on multiple terabyte filesystems.

libjackasyn is a library that allows you to use programs written for the OSS sound API with the JACK audio server. libjackasyn is a library that can be used for two purposes.
First it can be loaded via the LD_PRELOAD variable, turning OSS applications automatically into JACK-aware applications.
Second, it can be used to link against the program during build time, making it trivial to turn an OSS aware sound application into a JACK aware sound application in a short time.
libjackasyn got its name from the asynchronous manner in which it communicates with the JACK server, which means by using libjackasyn you will introduce an additional delay exactly the size of one JACK audiobuffer (1024 samples or 44 ms with the JACK default settings).
This delay can be reduced by reducing the JACK buffersize. It should not matter for sound generating applications, but it might introduce phasing effects when doing sound processing.
Enhancements:
- fixed RDONLY and WRONLY handling
- act upon jack shutdown, allows to switch between JACK and non-JACK operation
- several small bug fixes
- debug compilation optional

Sub::DeferredPartial is a deferred evaluation / partial application.

SYNOPSIS

use Sub::DeferredPartial def;

$S = def sub : P1 P2 P3 { %_=@_; join , @_{qw(P1 P2 P3)} };

print $S->( P1 => 1, P2 => 2, P3 => 3 )->(); # 123

$A = $S->( P3 => 1 ); # partial application
$B = $S->( P3 => 2 );

$C = $A + $B; # deferred evaluation

$D = $C->( P2 => 3 );
$E = $D->( P1 => 4 );

print $E->(); # force evaluation: 863

$F = $E - $D;

$G = $F->( P1 => 0 ) / 2;

print $G->(); # 400
print $G; # ( ( CODE(0x15e3818): P1 => 4, P2 => 3, P3 => 1 + CODE ...

$F->(); # Error: Free parameter : P1
$A->( P3 => 7 ); # Error: Bound parameter: P3
$A->( P4 => 7 ); # Error: Wrong parameter: P4

An instance of this class behaves like a sub (or, more precisely: subroutine reference), but it supports partial application and the evaluation of operators applied to such function objects is deferred too.

That means, evaluation has to be forced explicitly (which makes it easier to add introspection capabilities).

Objects that represent deferred (delayed, suspended) expressions are known as suspensions or thunks in various programming circles. Dont confuse with the same terms in the context of threads!