Free private eye game software for linux

This is an adapted, improved version of the popular javacave game, written in QtRuby.

Installation:

download
chmod +x snake(gl).rb
run it.

Quarters Board Game project is a strategy game for two players.

Although its rules are relatively simple, it still offers some of the same opportunities for skill as in chess.

This program was originally conceived in the summer of 1986 during a study of the mini-max algorithm for chess playing computers, and was thus designed to offer some of the same type of strategies.

The game was originally written in BASIC, then ported to Turbo Pascal, then to C, and finally to Java.

The Java version is not necessarily object oriented, since it is a crude port from the C version.

A Jacks Game is a real-time game that runs in a Web browser using the AJAX (Asynchronous JavaScript and XML) technology.

Multiple users can login in A Jacks Game to explore a common map and earn a common currency as their score.

A Jacks Game is free software released under GNU/GPL Open Source License.

Acquire is a computer version of the classic board game.
The goal of the game is to make the most profit by buying stocks in companies that form, merge and grow as tiles are placed on the game board.
This program is a text-based version of the game and should be playable on any system with a C++ compiler.
Enhancements:
- The main improvement of this release is that the bug causing the game to crash at the end was fixed, so you can now see who won.
- There were some other small bugfixes and changes.

Volity::Game is a base class for Volity game modules.

SYNOPSIS

See Volity::Game::TicTacToe and its source code for a simple but full-featured example.

This class provides a framework for writing Volity game modules in Perl. A Volity game module will be a subclass of this class.

To turn your subclass into an active Volity parlor, you can pass it to the volityd program via its game_class config option (see volityd).

USAGE

To use this module, subclass it. Create your own Perl package for your game, and have it inherit from Volity::Game. Then define game logic and other behavior primarily by writing callback methods, as described in "CALLBACK METHODS".

See Volity::Game::TicTacToe for a simple but complete example of a Volity::Game subclass.

Some things to keep in mind while writing your subclass:

Its a pseudohash

The object that results from your class will be a Perl pseudohash that makes use of the fields pragma. (See fields.) As the example shows, you should declare the the instance variables you intend to use with a use fields() invocation.

Other than that, an instance if your subclass will work just like a hash-based Perl object.

Use (but dont abuse) the initialize() method

The Volity::Game base class constructor calls initialize() as a final step.

If you override this method to peform game-specific initialization on your subclass, it must have a return value of $self->SUPER::initialize(@_).

Gallipoli: The Game is a stunning recreation of Australias greatest military adventure. As a commander in the Great War (WWI), you take on the role of leading the prime of Australias armed forces as they launch an all-out assault on the Central Powers (the Germans, Austrians and the Ottomans).
Gameplay is similar to the hit PC game, Lemmings, except, instead of trying to save your soldiers, your mission, as an authentic WWI commander, is to wipe out as many diggers as possible ... the more gruesomely, the better!
Main features:
- Landing at Hell Spit (ANZAC cove)
- Russells Top
- The Sphinx
- Walkers Ridge
- The landing at Sulva Bay
- The third wave at the Nek
Enhancements:
- game much faster
- more options
- Battle of Pozyers level removed (no-one was playing it)

The Eye Of Horus is a monitoring and alerting tool for computers. Its mainly useful for monitoring network services (eg, HTTP or SMTP servers) and the internal status of Unix servers (eg, load, disk usage, process counts).

In that respect, its a lot like Nagios, but in my opinion its better. It lacks a few features Nagios has, but it is a very simple architecture to which they can easily be added.

Its a flexible thing made from independent modules with well-defined interfaces, making it easy to customise and extend, but out of the box itll monitor your servers and produce a nice HTML summary of their status - OK, the looks need a bit of work, but that will come soon, and it can optionally integrate with the excellent (and I mean excellent) RRDTool to store logs of statistics (response times, number of packages with known security holes, etc) - and link from the status page to nice graphs of the historical behaviour of these statistics.

HOW IT WORKS

The core of the system is horus-check.py, a Python script which reads a configuration file (specified on the command line). The configuration file specifies a list of services - either network services, in which case the host to run the check from and the host to run the check at are specified, or local services, in which case only the host to run the check from need be specified. In either case, if the host to run the check from is not specified, then it defaults to the local host.

The service types reference definitions in a file which is referenced from the configuration file. In the service definitions file, a shell command to check the service is given; this command must output service status in a defined format, as a single-line YAML list. The list must contain, at least, a single-word status (OK, WARNING, FAILURE, or UNKNOWN), then optionally numeric statistics, then optionally a status message. For example:

[OK]
[UNKNOWN]
[OK, { load: 0.5, users: 3 }]
[WARNING, { load: 3, users: 30 }]
[FAILURE, { load: 95, users: 300 }]
[UNKNOWN, { }, Could not find AWK executable]

When a check is to be performed from a remote host, Horus opens an ssh connection to that host. It is assumed that the user horus is run as will have an ssh key set up to enable it to ssh to all such hosts without requiring a password.

Having performed the checks, horus-check.py then:

Reads in the status database named in the configuration file
Updates the status database with the new status of hosts
Computes an overall system status (the worst non-unknown status of any checked service)
Examines the service dependencies, and marks any service whose state is no worse than might be expected (eg, no worse than the worst state of a service it depends upon) are automatically marked as quiet
Computes a list of differences between the old and new status (services added, services removed, services whose status has improved, services whose status has worsened)
If there are any differences, invokes a notification script (named in the configuration file) with them, along with the overall status
Invokes a logging script (named in the configuration file) with the new value of every statistic reported by the service checks; I will soon provide a sample logging script that uses RRDTool to generate nice graphs.

The status database (which is written in YAML, so easily accessible to user scripts) can then be used to generate HTML status report (see status.cgi).