Free log files in sql server software for linux

RIPE Whois Server provides support for domain records and lookups.

This is a whois database server. The RIPE Whois server uses a backend SQL database to allow support for very large repositories. There is support for IPv6 records and lookups. Both RPSL and RIPE181 are supported.

Anemon Dhcp Servers goal is to create an implementation of the DHCP protocol under GPL and a lot of stuff around to facilitate network management.
The python sqlobject modules gives anemon the ability to use many database as backend (mysql, postgresql, mssql, sqllite, sybase, etc..)
The project is subdivised (at the moment) in 4 components :
- The Anemon Dhcp Server is a Python/SQL implementation of the DHCP server protocol
- The Anemon Web Center is a web management interface to Anemon Dhcp Server and MyDNS
- The Anemon Dhcp Client will be a Python implementation of the DHCP client protocol
- The Anemon Dhcp relay will be a Python implementation of the DHCP relay protocol

OpenVPN authentication server is a project which allows you to add very flexible authentication for your OpenVPN server.
OpenVPN authentication server provides very flexible authentication (LDAP, Kerberos, Radius, PAM, SASL, File, SQL, IMAP, POP3) for your OpenVPN server. You can also retrieve per-client configuration in your LDAP server.
Main features:
- Very flexible authentication configuration
- Chainable authentication backends. You can mix several authentication backends
- Authentication server written in perl
- Authentication server can run completely in chroot (recommended)
- Authentication client written in C
- Authentication client can run completely in chroot if OpenVPN server is chrooted
- Supports almost all existing authentication backends.
- Supported authentication backends:
- LDAP
- Kerberos5 (works also with Microsoft AD)
- any SQL database supported by perl DBI driver
- IMAPv4 server
- POP3 server
- plain file
- SASL library
- PAM library
- Radius service
- custom certificate validation algorithm.

Log::Dispatch::File::Alerts is a Perl object for logging to alert files.

SYNOPSIS

use Log::Dispatch::File::Alerts;

my $file = Log::Dispatch::File::Alerts->new(
name => file1,
min_level => emerg,
filename => Somefile%d{yyyy!!!!}.log,
mode => append );

$file->log( level => emerg,
message => "Ive fallen and I cant get upn" );

ABSTRACT

This module provides an object for logging to files under the Log::Dispatch::* system.

This module subclasses Log::Dispatch::File for logging to date/time stamped files. See Log::Dispatch::File for instructions on usage. This module differs only on the following three points:

alert files

This module will use a seperate file for every log message.

multitasking-safe

This module uses flock() to lock the file while writing to it.

stamped filenames

This module supports a special tag in the filename that will expand to the current date/time/pid.

It is the same tag Log::Log4perl::Layout::PatternLayout uses, see Log::Log4perl::Layout::PatternLayout, chapter "Fine-tune the date". In short: Include a "%d{...}" in the filename where "..." is a format string according to the SimpleDateFormat in the Java World (http://java.sun.com/j2se/1.3/docs/api/java/text/SimpleDateFormat.html). See also Log::Log4perl::DateFormat for information about further restrictions.
In addition to the format provided by Log::Log4perl::DateFormat this module also supports $ for inserting the PID and ! for inserting a uniq number. Repeat the character to define how many character wide the field should be.
A note on the !: The module first tries to find a fresh filename with this set to 1. If there is already a file with that name then it is increased until either a free filename has been found or it reaches 9999. In the later case the module dies.

Xplain2sql converts files from Xplain to SQL. xplain2sql supports a very large subset of Xplain, and it can convert from Xplain to Microsoft SQL Server, DB/2, Inprise InterBase, PostgreSQL, Oracle, MySQL, or ANSI-92 SQL.
It can also generate an XML description of the generated SQL. This XML description can be used to create low-level middle-tier code.
A Delphi/ADO XSLT style sheet is included. The C source code release should compile on any platform with an ANSI C compiler.
There are binary releases for FreeBSD, BeOS, Linux, and Windows 2000.
Xplain2sql supports a very large subset of Xplain already, and it is continually extended until full support is reached. Currently it can convert from Xplain to Microsoft SQL Server, Inprise InterBase, DB/2, PostgreSQL, Microsoft Access, and ANSI-92 SQL:
- Microsoft SQL Server support is very complete.
- Quite complete DB/2 support. Non literal inits are currently missing.
- InterBase support for init works only for literal inits (so attributes dont work). And because InterBase doesnt have the concept of temporary table, the extend and value only work for a single user.
- PostgreSQL is quite complete with the new PostgreSQL 7.3 release.
- Initial, but fairly complete Oracle support.
- Generates Microsoft Access data definition commands. However, it seems impossible to run an entire script against an Access database. Having to run each create table statement by hand is quite tedious.
- Generates good ANSI-92, however inits with non-literal values cannot be supported by ANSI-92 because it doesnt have the concept of before and after insert triggers.
Enhancements:
- Assert support was added.
- If-then-else is supported in init [default] statements for dialects that support triggers.

Since MySQL is the most popular SQL server that is used in conjunction with web sites, there was a need for incremental backup utility. ZZEE Active SQL Backup is designed for clients of web hosting companies, and can be useful to system administrators as well.
Main features:
- Can perform *incremental* backup of MySQL database
- Can perform full backup of MySQL database
- Can replicate database
- Can process SQL queries
- Can dump database structure
- Can suggest database changes needed to process incremental backup
- Can send data backed up by email
- Can transfer backed up data by FTP to other computer (if Net::FTP is installed)
- Can compress backed up data
Usage synopsis
Active SQL Backup can do incremental or full backups of MySQL database as often as needed. It is suitable both for the clients of web hosting companies who can not get access to MySQL update logs and for the host administrators. Backup syntax is:
shell> ./zmdb.pl -b
It stores backup files in BACKUP_DIR, specified in user_settings.txt, named like YYYY_MM_DD_hh_mm_ss.sql[.gz]. The backup files consist of series of SQL INSERT statements and may contain DELETE statements. The database scheme is stored in file database_name.create.sql. If gzip is available, then Active SQL Backup automatically uses it to compress stored data. The program can automatically send backed up files by email or upload to the other computer by FTP.
If the system fails, Active SQL Backup can restore the database. Restore syntax for incremental backups is:
shell> ./zmdb.pl -r
If you make full backups, restore syntax is the following:
shell> ./zmdb.pl -e < BACKUP_DIR/database_name.create.sql
shell> ./zmdb.pl -e < BACKUP_DIR/YYYY_MM_DD_hh_mm_ss.sql &
The first line is needed to restore database structure, and the second is the *most recent* data file. You may need to "gunzip" it before supplying to restore.
You can use the program to dump database structure
shell> ./zmdb.pl -s > structure_dump_file
or to process queries. The latter feature is useful if you need to process queries regularly, for example, to update membership status of the users of your online service. The syntax to execute SQL queries is:
shell> ./zmdb.pl -e < some_sql_file
Where format of some_sql_file is the same as with Mysql utility: SQL statements are separated by semicolon. Note that if you pass SELECT queries to Active SQL Backup, then no result will be returned.
Syntax summary is:
zmdb.pl [SINGLE_OPTION]
-a --advice suggest database modifications and tables_config.txt
-b --backup backup database structure and data
-e --execute execute SQL queries [from STDIN]
-h --help print this screen
-r --restore restore database structure and data
-s --structure dump database structure [to STDOUT]

Log::Log4perl is a Log4j implementation for Perl.

SYNOPSIS

# Easy mode if you like it simple ...

use Log::Log4perl qw(:easy);
Log::Log4perl->easy_init($ERROR);

DEBUG "This doesnt go anywhere";
ERROR "This gets logged";

# ... or standard mode for more features:

Log::Log4perl::init(/etc/log4perl.conf);

--or--

# Check config every 10 secs
Log::Log4perl::init_and_watch(/etc/log4perl.conf,10);

--then--

$logger = Log::Log4perl->get_logger(house.bedrm.desk.topdrwr);

$logger->debug(this is a debug message);
$logger->info(this is an info message);
$logger->warn(etc);
$logger->error(..);
$logger->fatal(..);

#####/etc/log4perl.conf###############################
log4perl.logger.house = WARN, FileAppndr1
log4perl.logger.house.bedroom.desk = DEBUG, FileAppndr1

log4perl.appender.FileAppndr1 = Log::Log4perl::Appender::File
log4perl.appender.FileAppndr1.filename = desk.log
log4perl.appender.FileAppndr1.layout =
Log::Log4perl::Layout::SimpleLayout
######################################################

ABSTRACT

Log::Log4perl provides a powerful logging API for your application