Free piknix hosting service software for linux

Nagios (formerly Netsaint) is a daemon written in C that is designed to monitor networked hosts and services.
Nagios project has the ability to notify contacts (via email, pager or other methods) when problems arise and are resolved. Host and service checks are performed by external "plugins", making it easy to write custom checks in your language of choice.
Several CGIs are included in order to allow you to view the current and historical status via a Web browser, and a WAP interface is also provided to allow you to acknowlege problems and disable notifications from an internet-ready cellphone.
Main features:
- Monitoring of network services (SMTP, POP3, HTTP, NNTP, PING, etc.)
- Monitoring of host resources (processor load, disk and memory usage, running processes, log files, etc.)
- Monitoring of environmental factors such as temperature
- Simple plugin design that allows users to easily develop their own host and service checks
- Ability to define network host hierarchy, allowing detection of and distinction between hosts that are down and those that are unreachable
- Contact notifications when service or host problems occur and get resolved (via email, pager, or other user-defined method)
- Optional escalation of host and service notifications to different contact groups
- Ability to define event handlers to be run during service or host events for proactive problem resolution
- Support for implementing redundant and distributed monitoring servers
- External command interface that allows on-the-fly modifications to be made to the monitoring and notification behavior through the use of event handlers, the web interface, and third-party applications
- Retention of host and service status across program restarts
- Scheduled downtime for suppressing host and service notifications during periods of planned outages
- Ability to acknowledge problems via the web interface
- Web interface for viewing current network status, notification and problem history, log file, etc.
- Simple authorization scheme that allows you restrict what users can see and do from the web interface
Enhancements:
- Fixed bug with processing epn directives in Perl plugins
- Fixed bug with check_result_path config option being ignored
- Added $MAXHOSTATTEMPTS$ and $MAXSERVICEATTEMPTS$ macros
- Fixed bug with incorrect output returned from embedded Perl plugins
- Fixed bug where status data file was not read by CGIs using mmap()
- Fix for CGI segfault
- Program status now updated at least every 5 seconds for addons that watch NDOUtils DB
- Added escape_html_tags option to CGI config file to escape HTML tags in plugin output
- Added optional integration with Splunk into the CGIs
- Added new action and notes URL target frame options to CGI config file
- Added new exclude option to timeperiod definitions for easy on-call rotation definitions

adcfw-log is a tool for analyzing firewall logs in order to extract meaningful information.
It is designed to be a standalone script with very few requirements that can generate different kinds of reports, such as fully formatted reports of what had been logged, with summaries by source or destination host, the type of service, or protocol.
There are also options to filter the input data by date, host, protocol, service, and so on.
Only netfilter log format is supported at this time.
Main features:
- support for netfilter log format
- log entries filtering based on protocol, source host, destination host, service, prefix, input and output interfaces
- specific reports based on protocol, source or destination hosts, service
- summaries based in source host, destination host, service and prefix

Host on Imageshack is a service menu tor upload images on Imageshack.

The tarball contains the .desktop file, the original script and an icon (modified version of Azureus icon).

Based on imageshack_upload.sh -> http://www.bchesneau.info/articles/2006/10/23/bash-script-to-upload-image-to-imageshack

The tarball content:

#NAME #CONTENT #DESTINATION

1.imageshack.desktop the servicemenu file ~/.kde/share/apps/{konqueror|dolphin}/servicemenu
2.imageshack.png an icon for the menu ~/.kde/share/icons
3.imageshack_upload the original bash script ~/bin
4.README this file

Incredible Hosting System is a tool that allows you to administrate a hosting system using a Web browser.
The aim is to support administrators and users. Incredible Hosting System currently includes support for Virtual Qmail.
IHS will be a platform for implementing and integrating mail or hosting systems in different environments - small or medium companies looking for tools for managing system accounts, hosting companies offering services based on this system.
System is complex, requires integration of many other applications, for example: WWW server, mail transfer agent, FTP server, database. Also it should be possible to integrate system with other applications that are specific to companys environment.
Aside integration of existing application platform must be built that will allow to manage everything is a manner undependent from tools that are used in background. It should be a centralized and consistent environment. Also API for developers shoule be generic that changes in tools doesnt require changes in code.
Incredible Hosting System will be based on following tools, technologies:
- Apache as WWW server;
- PostgreSQL as default database;
- ProFTPD as default database;
- qmail or Virtual Qmail as a MTA;
- CORBA as a service communication protocol;
- J2EE as an runtime environment;

Riverdrums Load Balancer project is a no-frills, event-driven load balancer aimed at clarity and efficiency.

Compiling:

1. Install libevent
2. gcc -Wall -O2 -o rlb rlb.c -levent
Solaris:
a) cc -Wall -O2 -o rlb rlb.c -lnsl -lsocket -levent

Usage:

$ rlb -p port [-b addr] [-B addr] -h host:service[:max] [-h host:service[:max] ...] [-m max] [-t timeout] [-c check interval] [-s bufsize] [-n servers] [-f]

Avahi is a framework for Multicast DNS Service Discovery on Linux.
It allows programs to publish and discover services and hosts running on a local network with no specific configuration.
For example, you can plug into a network and instantly find printers to print to, files to look at, and people to talk to.
Main features:
- Licensed under LGPL
- IPv4 and IPv6 support
- DBUS interface
- Drops all priviliges and runs as user "avahi"
- Embeddable mDNS stack (i.e. mDNS stack available as library)
- Support for loading static service definitions from XML fragments
- Interface to GLIBC NSS using [WWW]nss-mdns
- Ability to reflect mDNS traffic between multiple subnets
- Ability to configure a unicast DNS server automatically from server data published on the LAN

Wombat is a servlet container for Perl. It is not an executable program itself; rather, it is a library that can be used by programs to embed a servlet container. Embedding programs must provide implementations of Connector API classes that adapt Wombat to the surrounding environment. One such connector is Apache::Wombat which embeds a Wombat servlet container within an Apache httpd built with mod_perl.

Currently no developer documentation for Wombat itself is provided beyond the contents of this document and the POD for each Wombat class.

CONTAINER CONFIGURATION

CONTAINER DIRECTORIES

Web application directories are generally located beneath a single application base directory which in turn is usually located beneath the containers home directory. Each Host configured in the container can use the same application base directory (called webapps by default) or provide its own, possibly located outside the containers home directory. As well, each Application configured in the container has the option of locating its webapp directory outside its Hosts application base directory.

A typical directory structure for Wombat embedded within Apache/mod_perl might be:

# containers home dir
/usr/local/apache
# default hostss appbase dir
/usr/local/apache/webapps
# examples apps webapp dir
/usr/local/apache/webapps/examples
# another hosts appbase dir
/home/bcm/maz.org/webapps
# another apps webapp dir
/home/bcm/maz.org/webapps/comics

CONTAINER DEPLOYMENT DESCRIPTOR

The behavior and attributes of the Wombat servlet container are controlled by a container deployment descriptor (usually named server.xml). This file is modeled after the Tomcat 4 equivalent, but it does have slight differences. A full Configuration Guide will be published; until then, the definitions included below are the only documentation:

Elements supported in server.xml (named with XPath paths, example attribute settings included inline):

Server

Represents the entire perl interpreter, into which one or more Services are deployed. Only one Server may be specified.

Server/Service

Represents a collection of one or more Connectors that share a single Engine (and therefore the web applications visible within that Engine). A display name for the Service (name="HTTP Service") may be specified. Many Services may be specified for the single Server.

Server/Service/Connector

Represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to its associated Container for processing. The name of a class that implements the Wombat::Connector interface MUST be specified (className="Apache::Wombat::Connector"), as well as a scheme (scheme="http" attribute) and any attributes needed by the implementation. A secure flag (secure="1") may also be set to indicated that the request was transported using SSL. Many Connectors may theoretically be specified for a particular Service, but at this time, the Wombat internals need some refactoring before they can support Connectors for protocols other than HTTP.

Server/Service/Engine

Represents the highest level Container associated with a set of Connectors. The Engine discriminates between virtual hosts as necessary and passes the request along to the appropriate Host. A display name for the Engine (name="Apache-Wombat") may be specified, as well as the name of a default host (defaultHost="localhost" attribute) to receive requests that are not mapped to other specifically configured Hosts. Only one Engine may be specified for a particular Service.

Server/Service/Engine/Logger

Unless overridden in a lower level Container, all log messages will be handled by this Logger. The name of a class that implements the Wombat::Logger interface MUST be specified (className="Apache::Wombat::Logger"), as well as any attributes needed by the implementation. A minimum log level (level="DEBUG") may also be specified. If no Logger is specified, logging will be disabled for the Container. Only one Logger may be specified for a particular Container.

Server/Service/Engine/Realm

Unless overridden in a lower level Container, all web applications will be subject to this security Realm. The name of a class that implements the Wombat::Realm interface MUST be specified (className="Wombat::Realm::DBIRealm"), as well as any attributes needed by the implementation. If no Realm is specified, security will be disabled for the Container. Only one Realm may be specified for a particular Container.
Note that security MUST be also enabled in a particular web applications deployment descriptor in order for the Realm to be relevant to that web application. Therefore a Realm may be configured for an entire Container but only in use for a single Application.

Server/Service/Engine/SessionManager

Unless overridden in a lower level Container, all sessions will be managed by this SessionManager. The name of a class that implements the Wombat::SessionManager interface MUST be specified (className="Wombat::SessionManager::StandardSessionManager"), as well as any attributes needed by the implementation. A maximum inactivity interval/idle out time may also be specified (maxInactiveInterval="300"). If no SessionManager element is specified, sessions will be disabled for the Container. Only one SessionManager may be specified for a particular Container.

The type of SessionManager used will depend heavily on the environment provided by the embedding program. For instance, a multiprocess Apache/mod_perl server embedding Wombat will require a SessionManager that caches sessions in shared memory, on disk or in some other location that all processes can access, whereas a multithreaded daemon embedding Wombat might use a simple memory-based SessionManager.

Server/Service/Engine/Valve

Represents a request-processing component that "wraps" around the Servlet that is ultimately responsible for processing the request. The name of a class that implements the Wombat::Valve interface MUST be specified (className="Wombat::Valve::RequestDumperValve"), as well as any attributes needed by the implementation. Many Valves may be specified for a single Container.

Valves are used to add container functionality for specific Containers, much like Filters are used to add application functionality for specific Servlets. An example of a commonly-used Valve might be a one that logs information about each request (an AccessLogValve perhaps).

Server/Service/Engine/Host

Represents a Container associated with a particular virtual host. A Host maps the request URI to a particular web application and passes the request along to the appropriate Application. The name of the host MUST be specified (name="localhost"), as well as the application base directory (appBase="webapps") which can be specified absolutely or relative to the containers home directory. Many Hosts (at least one, corresponding to the Engines default host attribute) may be specified for a single Engine.

Server/Service/Engine/Host/Alias

Represents an alternate name or names for the virtual host. For a Host named maz.org, the Alias *.maz.org might be configured to catch requests for specific hosts and subdomains in the domain. The name of the alias MUST be specified (name="*.maz.org"). Many Aliases may be specified for a particular Host.

Server/Service/Engine/Host/Logger

A Logger configured for a Host overrides any Logger configured at the Engine level.

Server/Service/Engine/Host/Realm

A Realm configured for a Host overrides any Realm configured at the Engine level.

Server/Service/Engine/Host/SessionManager

A SessionManager configured for a Host overrides any SessionManager configured at the Engine level.

Server/Service/Engine/Host/Valve

Any Valves configured for a Host add to (and execute after) any Valves configured at the Engine level.

Server/Service/Engine/Host/Application

Represents a Container associated with a particular web application. An Application inspects the request URI and passes the request along to the appropriate Servlet (as configured in the web applications deployment descriptor). The display name of the application (displayName="Examples Application") and the URI path base for the application (path="/wombat-examples") MUST be specified, as well as the webapp directory (docBase="examples") which can be specified absolutely or relative to the parent Hosts application base directory. Many Applications (at least one, corresponding to the URI path /) may be specified for a single Host.

Server/Service/Engine/Host/Application/Logger

A Logger configured for an Application overrides any Logger configured at a higher level.

Server/Service/Engine/Host/Application/Realm

A Realm configured for an Application overrides any Realm configured at a higher level.

Server/Service/Engine/Host/Application/SessionManager

A SessionManager configured for an Application overrides any SessionManager configured at a higher level.

Server/Service/Engine/Host/Application/Valve

Any Valves configured for an Application add to (and execute after) any Valves configured at a higher level.