Free server virtualization software for linux

Server Monitor is a theme which displays the status of your servers. Also you can start / stop them by clicking the names.

You cann add servers by editing the py-file. You may resize theme in the .theme-fille.

Based on vpn by N7DR (http://www.kde-look.org/content/show.php?content=39390).

QEMU Server Tools is a set of simple command-line scripts for managing multiple QEMU VMs easily without requiring a graphical frontend.

QEMU Server Tools organizes VMs into directories and mimics the usage of command line tools from VMware Server.

DeniX Server OS is an independent Linux based distribution built from scratch by Denis Salmanovich. They aim to offer a user-friendly full-featured server operating system, pre-configured, well structured and easy to work with, and filled with the latest stable versions of Linux apps.
Its easy to install and configure. Every package is downloaded from the authors source and compiled when installed.
Main features:
- Domain Controller
- ADSL/CABLE Router (PPPoE)
- Network Firewall
- Anti Virus Gateway
- Anti Spam Gateway
- Mail Server (local & external) + Web Mail
- Calendar Sharing Support
- Network File Server
- DHCP Server
- TFTP BOOT Server
- WINS Server
- FTP Server
- VPN Server
- DNS Server
- DDNS Server
- MySQL Server
- HTTP Apache Server
- Remote Backup Solutions
- Remote control and administration
- Print Queue Server
- Proxy Server

Net::Server is an extensible, general Perl server engine.
SYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).

NNML::Server is a minimal NNTP server.

SYNOPSIS

perl -MNNML::Server -e server
perl -MNNML::Server -e unspool

NNML::Server server implements a minimal NNTP server. It is (hope-) fully conformant to rfc977. In addition the commands XOVER and AUTHINFO are implemented.

Supported commands:

ARTICLE, AUTHINFO, BODY, GROUP, HEAD, HELP, IHAVE, LAST, LIST,
MODE, NEWGROUPS, NEWNEWS, NEXT, POST, QUIT, SLAVE, STAT

XOVER, XHDR, LIST NEWSGROUPS ng-spec

The main reason for writing this was to synchronize my mail directories across different hosts. The Mail directories are MH-Style with a .overview file in each folder and an active file in the base directory. These are maintained by the Emacs Gnus backend NNML. To get started, you can generate/update this files using the overview program. Upon POST and IHAVE commands this files will also be updated.

To start from scratch use:

touch /tmp/active;
perl -MNNML::Server -e server(base => "/tmp", port => 3000)

To export your mh-Mail use:

perl overview -base ~/Mail
perl -MNNML::Server -e server(base => "$ENV{HOME}/Mail", port => 3000)

The command POST and IHAVE honour the Newsgroups header if not overwritten by the X-Nnml-Groups header. Articles will contain an appropriate X-Nnml-Groups header when retrieved by message-id.

When the client submits the SLAVE command, all forther post requests are spooled in $Config-spool> (usually ~/Mail/NNML.spool) for performance reasons. You can process the spooled articles by submitting the XUNSPOOL command or by calling

perl -MNNML::Server -e unspool

Rejected articles will be saven in $Config-bad> (usually ~/Mail/NNML.bad)