Free server log software for linux

mergelog provides a fast tool to merge HTTP log files by date.
mergelog is a small and fast C program, which merges HTTP log files by date in Common Log Format (Apache default log format) from Web servers, behind round-robin DNS.
It has been designed to easily process huge logs from highly stressed servers, and can manage gzipped files.
Enhancements:
- dont abort anymore on corrupted log lines
- set BUFFER_SIZE value to 32Ko
- fixed a major bug on a broken month initialization
- corrections on manpages
- fix in configure.in to abort if zlib is not present
- fixed a potential segmentation fault on malformed log lines
- autoconf compliant thanks to Igor Genibel

Tail server allows you to export the output of a "tail -f" command of a log file to a TCP port, allowing it to be viewed remotely with telnet. Tail Server provides a regular expression filter to include or exclude output view.
In several circumstances the need to access on remote time-varying log file leads to write some simple scripts.
These files generated by applications like syslog, http, news, etc. are often located on different machines.
System Administrator usually logon on remote system then type:
# tail -f filename
Tail Server offers the possibliy to map on Tcp/Ip port the output of "# tail -f filename" without (each time) logging on remote systems.
Also offers output regular expressions filter in order to include or exclude strings.
Enhancements:
- Server Log File has been implemented.

C++ Server Pages is a partial Java server pages and servlet implementation in C++. C++ Server Pages is written as Apache 2.0 modules, with the focus on performance.

Simple Log is a small library that does logging very simply and requires you to do almost nothing (other than actually logging) to get log output to happen. Simple Log is much simpler to use than a logging framework, especially in terms of configuration.
It doesnt attempt to solve every logging problem in one package, but contains enough features to be a viable alternative for most applications that need logging. This tool will handle the logging needs of most small- to large-sized projects, but with an almost non-existent learning curve.
Enhancements:
- This release is primarily about the addition of log rolling (by time of day, file size, or custom strategy), the inclusion of a small but humorous user guide, the fixing of a raft of minor bugs, and the inclusion of a few other small features increasing flexibility.

Run a web server inside LAN is a simple script to run a WWW server inside a Local Area Network. Run a web server inside LAN script assume all iptables features are compiled statically in the kernel, or all modules are loaded.

Otherwise you may encounter some surprises trying to utilize the more featureful and creative commandlines that Ive come up with.

Sample:

#external and internal interfaces
EXT=eth0
INT=eth1

# clear everything, and create my cascading chains
iptables -F
iptables -N e0
iptables -N tcpin
iptables -N udpin

# e0 is the name of our chain for eth0
iptables -I INPUT -i $EXT -j e0

# OUTPUT Chain
iptables -A OUTPUT -o $EXT -j DROP -p icmp --icmp-type ! echo-request

# remote gnutella queries were really pissing me off one day
# iptables -A OUTPUT -o $EXT -j DROP -p tcp ! --syn --dport 6346
# iptables -A OUTPUT -o $EXT -j DROP -p tcp ! --syn --sport 6346

# $EXT Chain
# a single rule to accept SYN Packets for multiple ports (up to 15)
iptables -A tcpin -j ACCEPT -p tcp --syn -m multiport --destination-ports 873,993,995,143,80,113,21,22,23,25,53

# stateful connection tracking is wonderful stuff
# ESTABLISHED tcp connections are let through
# If we send a SYN out, the ACK is seen as RELATED
# then further communication is accepted by the ESTABLISHED rule
iptables -A e0 -j ACCEPT -m state --state ESTABLISHED
iptables -A e0 -j ACCEPT -m state --state RELATED

# certain ports I simply DROP
iptables -A tcpin -j DROP -p tcp --syn -m multiport --destination-ports 6346,139

# UDP rules...
iptables -A udpin -j DROP -p udp -m multiport --destination-ports 137,27960

# I run a DNS server, so we must accept UDP packets on port 53
iptables -A udpin -j ACCEPT -p udp -m state --state NEW --destination-port 53

# lets log NEW udp packets on ports 1024:65535, then let them through
iptables -A udpin -j LOG -p udp -m state --state NEW --destination-port 1024:65535 --log-level debug --log-prefix UDPNEW --log-ip-options
iptables -A udpin -j ACCEPT -p udp -m state --state NEW --destination-port 1024:65535

# lets log NEW tcp packets on ports 1024:65535, then let them through
iptables -A tcpin -j LOG -p tcp --syn --destination-port 1024:65535 --log-level debug --log-prefix TCPNEW --log-tcp-options --log-ip-options
iptables -A tcpin -j ACCEPT -p tcp --syn --destination-port 1024:65535

# lets log INVALID or NEW tcp packets on priveleged ports, then DROP
# (remember I have certain ACCEPT rules higher up the chain)
iptables -A tcpin -j LOG -p tcp -m state --state INVALID,NEW --destination-port 1:1023 --log-level warn --log-prefix TCPPRIV --log-tcp-options --log-ip-options
iptables -A tcpin -j DROP -p tcp -m state --state INVALID,NEW --destination-port 1:1023

iptables -A e0 -p tcp -j tcpin
iptables -A e0 -p udp -j udpin
iptables -A e0 -j LOG --log-level debug --log-prefix NETFILTER --log-ip-options -m state --state INVALID,NEW
iptables -A e0 -j DROP

# NAT Rules
# I run a web server inside...
iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 80 -j DNAT --to-destination 192.168.1.4:80

Dwarf HTTP Server is a full-featured and ready-to-use web server with the Java Servlet API 2.2 and Java Server Pages 1.1 implementation.
Dwarf HTTP Server can be used either standalone or embed in a larger hosting application, free of charge for the binary redistribution
Since the server is based on the Dwarf framework, it shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- multi-threaded design
- dynamically adjusted number of active threads
- Java Servlet API 2.2 implementation
- Java Server Pages 1.1 (by Apache Tomcat/Jasper)
- HTTP/1.1 and CGI/1.1 implementation
- WebDAV Class 1 implementation
- built-in SSL/TLS support
- IP-based and name-based virtual hosts
- customizable authentication and authorization
- standard and custom HTTP log formats
- extensible session management
- Basic and Form-based HTTP authentication
- automatic deploying of WAR archives
- runtime server configuration
- full documentation with guides and tutorials
- web application examples with source code

SaxenOS Desktop Server is as it seems the first working Live CD with a running LTSP Linux Terminal Server. This means you can serve thin client PCs from a live CD.
Usernames and Passwords:
After booting from the live CD you get the login Screen. On the desktop its XDM, on the Desktop Server its GDM. Use the following username/password combinations to login.
Desktop Server:
User: root, Password: root
User: demo, Password: demo
User: demo1, Password: demo1
User: demo2, Password: demo2
After installation please change these passwords!!!
Enhancements:
- The SaxenOS 2 ISO image is now down to a 534 MB and needs about 1.7 GB space on the target partition plus the space for home directories and temporary and log files - so a 2 GB partition is still the minimum. Changes: fixed German installer translations; changed formatting of target partition to ext3; removed win32 Codecs - theyre now a separate installer download (for legal reasons); removed REALbasic - check the installer downloads next week; new SaxenOS System Panel, written in REALbasic.