Free grim reaper tattoos software for linux

SMTP Relay Checker is a fully configurable, multithreaded open mail relay scanner. It supports scanning of IP blocks, and can print the results to a Web page.
SMTP Relay Checker is intended for Systems Administrators to check IP blocks under their control.
Compilation / Installation
To build SmtpRC please run "make" in the package directory. This will build the package and create the binary "smtprc". To install the package, please run "make install".
By Default, the binary will be installed into /usr/local/bin/, configuration files will be installed under /usr/local/etc/smtprc/ and all documentation files will be installed under /usr/local/share/doc/smtprc/. Please see below for a full list of installed files.
/usr/local/bin/smtprc
/usr/local/bin/gsmtprc
/usr/local/etc/smtprc/auto.conf
/usr/local/etc/smtprc/email.tmpl
/usr/local/etc/smtprc/rcheck.conf
/usr/local/share/doc/smtprc/README
/usr/local/share/doc/smtprc/FAQ
/usr/local/man/man1/smtprc.1
/usr/local/man/man1/gsmtprc.1
Using Smtprc
SmtpRC can be run by specifying options on the command line, or by configuring an "auto configuration" file and letting SmtpRC parse the options from there. The latter is recommended.
When SmtpRC is installed, a example "auto configuration" file is installed in "/usr/local/etc/smtprc/auto.conf". Edit this file, changing the values to suit your specific network requirements and run smtprc with the following option (a full list of options
is detailed below):
"/usr/local/bin/smtprc -j /usr/local/etc/smtprc/auto.conf"
To be sure that a mailserver relays third-party email, SmtpRC will attempt to relay mail to an address specified. It is recommended that this address is a mailbox on the local machine that is being used to run SmtpRC - pop support is a planned feature, but for now, SmtpRC only supports checking local mailboxes (mbox and Maildir). Create a new user account (smtprc), specify the email address for this account, and the local mailbox (on the command line or in the "auto configuration" file), and SmtpRC will attempt to relay emails to this address and check for recieved emails after scanning.
There is also a GUI interface to smtprc (gsmtprc) that is installed in /usr/local/bin. This requires Perl Tk to run.
Enhancements:
- Fixes a race condition between the master and reaper threads.

DWI is an experimental platform for exploring ways of making application development simpler. It is still hard to write large, complex, multi-user, data-driven (SQL-backed) applications.
It doesnt matter if your development platform is the web and Enterprise Java Beans, C# and .net or Mono, or whether its the Gnome/GTK or KDE widget set and the Linux desktop; its still just plain hard.
DWI is an effort to change this situation. DWI currently offers a simple way of developing data-driven (that is, SQL-backed) Gnome applications (designed with the Glade GUI designer).
It does this by avoiding "programming" (or at least, "traditional programming" in C. C#, perl, python or any other "traditional" language), substituting instead a configuration-file like format that defines how various GUI elements should be hooked up to various objects (such as GLib GObjects) or SQL fields and tables.
The current primary effort with DWI is to provide a number of well-documented, easy-to-understand, working examples that show how to use DWI. These examples currently include a stand-alone bug-tracker-like application, examples of integrating with existing GTK applications, and an example of hooking up a Glade-designed interface to a GLib GObject with almost no C programming at all (assuming you have a GLib GObject already handy.
DWI is a fairly simple environment for quickly creating data-driven applications, that is, graphical applications that manipulate and show info from a database. This environment differs from others in that it is focused on native GTK/Gnome support through the Glade GUI designer, and thus allows you to build user interfaces as elegant as you can make them in Glade.
At this point, this system has enough features to be adequate for creating form-editing and reporting applications. Multiple SQL database vendors are supported through ODBC or libdbi drivers. There is a simple db-driver infrastructure so its easy to support for additional SQL APIs. The system supports all of the basic Gtk widgets, and an additional half-dozen Gnome I/O widgets, such as GnomeDateEntry.
DWI is powered by an engine that has some fairly generic procedures for mapping fields, such as SQL table columns or widget values, between each other, and also between other things, such as objects, hash tables and etc. In a certain sense, the engine can be thought of as an Object-to-Relational Mapping (ORM), mapping SQL to several object systems, including Glib GObjects and QOF. This engine has been designed so that it becomes easy to add support for all kinds of new object systems: i.e. for the engine to be a generic re-mapper between not just SQL and GTK but between many different types of object systems and data sources/sinks.
Built on top of this engine is a DWI application that parses an XML-based file, the "DWI file", that describes the connections between glade widgets (or objects in general) and database tables. Currently, the only way to create DWI files is by hand. Unfortunately, this can be a fairly long and laborious process itself, especially when creating something a bit more sophisticated. In the future, we hope to have an extension to Glade, or possibly an extension to a database-browsing tool that will allow you to graphically make such connections. (Work has begun on such a tool, written in DWI itself).
The grim reality is that DWI wont ever become popular without a graphical designer. Although fairly complex apps can be readily created using DWI, it does have a non-trivial learning curve. When we say "can be created quickly", we mean "days" or "weeks", as opposed to "months" for traditional database application development cycles. Graphical RAD tools have a way of being brainlessly pleasant to use, and give the impression of an even faster development cycle, even though the learning curve is identical.
Note that the design of the XML format is sufficiently generic that it is not directly tied to Glade. It should be straightforward to adopt other ORM markups to inter-operate with the DWI engine. It is also envisioned that other GUI object systems, such as PHP, could be used with DWI, so as to create data-driven web pages. That is, Glade is currently the only GUI driver, but other drivers for other GUIs should be possible.
Enhancements:
- Changed to use automake Makefile system for easier installs; make install target now works.
- Segregate gtk and qof features to own subdirectories, so that apps which do not nead gtk do not need to link to the gtk libraries.
- Add support for QOF objects, including multiple examples of using QOF.
- Finish modularize of the SQL db drivers, so that only the required driver is actually loaded.

mysqlrowcopy is a tool that generates insert statements from result sets. It produces output similar to what might result from running mysqldump on a single SELECT query.

This project helps eliminate some of the tedium of moving data between QA and production MySQL databases.

Build:

To build mysqlrowcopy, you should run:

./configure
make

A mysqlrowcopy and mysqlrowcopy.debug file are created. They have identical functionality, the .debug version simply has debugging symbols built in (for gdb).

Since mysqlrowcopy is probably going to be I/O bound with modest CPU and RAM usage, the only reason to even build a 64-bit version is to work around potential issues in dynamic linking 32-bit binaries against 64-bit libraries.

RECIPES

1. Migrating a MySQL user account reaper from QA server to a production server.

e.g. MySQL database server qa3.example.com to prod1.example.com:

$ mysqlrowcopy -h qa3.example.com
SELECT * FROM db WHERE User = "reaper" mysql db > reaper.sql
$ mysql -h prod1.example.com mysql < reaper.sql

You could of course simply pipe the output of mysqlrowcopy into mysql and skip the intermediate file.

(Dont forget to RELOAD PRIVILEGES afterwards)

2. Keep your test environment up to date. Populate it with production data every 24 hours. You could run this sequence from cron once a day:

$ mysqlrowcopy -h finance-db.example.com
SELECT * FROM stocks WHERE modified > DATE_SUB(NOW(),INTERVAL 24 HOUR)
finance stocks > day-stocks.sql

$ cat day-stocks.sql | mysql -h finance-test.example.com finance

3. Copy data between tables on different servers that have some similar fields.

Youve got common data in table Zip on a production database:

mysql> desc Zip;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | PRI | | |
| ZIPCodeType | char(1) | YES | | NULL | |
| City | varchar(32) | YES | | NULL | |
| CityType | char(1) | YES | | NULL | |
| State | varchar(32) | YES | | NULL | |
| StateCode | char(3) | YES | | NULL | |
| AreaCode | char(3) | YES | | NULL | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
9 rows in set (0.00 sec)

And youve got table ZipPosition in a research database:

mysql> desc ZipPosition;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | | | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

You want to load data from production Zip into research ZipPosition.

$ mysqlrowcopy -h production SELECT ZIPCode,Latitude,Longitude common ZipPosition > pos.sql
$ cat pos.sql | mysql -h qa research

Note how we specify ZipPosition on the first line to tell mysqlrowcopy what the destination table is going to be.