Free startup software for linux

SYNOPSIS
######
# Subroutine interface
#
use Data::Startup qw(config override);
$options = override(%default_options, @option_list );
$options = override(%default_options, @option_list );
$options = override(%default_options, %option_list );
@options_list = config(%options );
($key, $old_value) = config(%options, $key);
($key, $old_value) = config(%options, $key => $new_value );
($key, $old_value) = config(%options, $key => $new_value );
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, %option_list);
######
# Object interface
#
use Data::Startup
$startup_options = $class->Data::Startup::new( @option_list );
$startup_options = $class->Data::Startup::new( @option_list );
$startup_options = $class->Data::Startup::new( %option_list );
$options = $startup_options->override( @option_list );
$options = $startup_options->override( @option_list );
$options = $startup_options->override( %option_list );
@options_list = $options->config( );
($key, $old_value) = $options->config($key);
($key, $old_value) = $options->config($key => $new_value );
($key, $old_value) = $options->config($key => $new_value );
@old_options_list = $options->config(@option_list);
@old_options_list = $options->config(@option_list);
@old_options_list = $options->config(%option_list);
# Note: May use [@option_list] instead of @option_list
# and {@option_list} instead of %option_list
Many times there is a group of subroutines that can be tailored by different situations with a few, say global variables. However, global variables pollute namespaces, become mangled when the functions are multi-threaded and probably have many other faults that it is not worth the time discovering.
As well documented in literature, object oriented programming do not have these faults. This program module class of objects provide the objectized options for a group of subroutines or encapsulated options by using the methods directly as in an option object.
The Data::Startup class provides a way to input options in very liberal manner of either
- arrays, reference to an array, or reference to hash to a
- reference to an array or reference to a hash
- reference to a hash
- referene to an array
- many other combos
without having to cut and paste specialize, tailored code into each subroutine/method.

Game Server Startup Script project is a startup script to manage dedicated game servers like Quake3.
Game Server Startup Scripts is a startup script to manage a wide variety of Linux dedicated game servers. It can start/stop/restart/fix dedicated game servers like Quake3, Half Life, Tribes 2, UT2K4, BF1942 and others.
It uses qstat through cron to validate that a game is running as expected. If a game is not running as expected, the game is automatically restarted from the script through cron.
GSSS was written becuase I wanted a way to start up a variety of games in a standard way. Then I also wanted to make sure the games stayed running even after a crash.
So I wrote this perl script. It will start games and through a cron job make sure they stay running. If you have qstat installed it can also verify the game is running like it is suppose to be and not in some strange state where no one can play.
If the game is running but unresponsive, it kills it and starts it again. You can also stop running games cleanly as well.
Games supported by "Game Server Startup Script":
- Quake2
- Quake3
- RTCW
- Half Life
- Unreal
- UT2K3
- UT2K4
- Tribes 2
- NWN
- BF1942
- ET
Enhancements:
- Very minor changes, minor readme changes, clean up

Shttp is a partial implementation of HTTP/1.1. The project does not conform to the RFC but works well enough to serve static content in a experimental/educational context.

The module consists of well under 1000 LoC making it an excellent example of what can be done with ServerKit with little effort and a great learning tool for those getting started with ServerKit programming.

Usage:

It is advised that you read the ServerKit documentation before trying to use this module, as most of the basic usage is simply using ServerKit, nothing specific to this module.

Due to the simple nature of this module it does not include a personality template and it is not expected that you would use it under daemontools.

Instead, the module sources include a simple startup script to run it "in-tree" without installing it in the system. There is still a c11n file included which gets used "in-tree" as well. See below for the configuration options.

CrystalAudio is a FVWM-Crystal configuration tuned for use on an audio workstation. It has many new applications for the menu, including many sound-related applications and improved sound controls. The project launches qjackctl at startup.
The final goal of the project is to make the FVWM-Crystal menu compatible with the freedesktop specification and to provide some tools to generate the menu entries and icons from desktop and icon files provided by the applications in the system.
Enhancements:
- generate-fvwm-crystal-menu work with both new and old type application desktop files, so it is time for the 2.0 version.
- A lot of debugging have been done on that script: See the ChangeLog for the details.
- Added support for stalonetray in all the recipes.

XChat2 plugin helps you to use BMPx from within XChat, including remote control, add files to playlist from file or library, select bookmarked audio stream and having XChat interact with your IRC channel (displaying current track played) with a customizable look.

Usage:

You need to have Python plugin loaded first and then load bmp-xchat-plugin.py file. To autoload the plugin at startup, just copy it to your ~/.xchat2 directory. Then run /bmp help in xchat to have the list of supported commands.

Tecnoupman project is a manager/monitor for the UPS Tecnoware Adv. Tecnoware (FIRENZE), only supplies a payment proprietary cable and software.
So, even if the UPS is equipped of RS-232 interface its not possible, without spent a lot of money, to manage the UPS directly from the PC.
Ive tried several times to contact the Tecnoware (firenze), but ive obtained zero support and zero technical infos about the UPSes and the cables pinouts. The cable, in fact, is a non standard one.
USAGE:
After that youve compiled the sources, and connected the UPS to Serial Port, youre ready to use the manager/monitor. Tupsmand is the core of the system. It can monitor and manage the power and the shutdown of the server/ups.
Youve to startup the daemon using a command like:
revolution#tupsmand /etc/tupsmand.conf
after startup, tupsmandll daemonize monitoring all the parameters from the
UPS. All paramters for the startup, must be specified in the config file:
tupsman.conf, like this format:
DEBUGL=1<<less