Free many times software for linux

Timbersee is a program very similar to the swatch program. Its used to monitor logfiles for important messages using regular expressions, but differs in that it can watch more than one logfile at a time, and does not fork off extra processes.
In practice, timbersee is a security tool to assist system administrators in weeding through the zealous informational reporting by various programs into the system logs.
Many times, problems reported to syslog are "lost in the noise", especially since most administrators dont make it a habit to keep up with all the various logfiles.
By allowing the administrator to define which messages are not important, tools like timbersee promote the habit of keeping a watchful eye on ones machines.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- fixed the timeout property of to make more sense.
- added --quit option, so that init scripts can test the config file and generate messages to stderr.

APbyAS provides Italian Web-based process re-engineering support.

Each employee survey his own real job and registers activities and times on weekly and annual basis. Results are summarized per unit and whole organization, with totals and averages.

TRASHY is a way to write HTML code using only a few characters, reducing the amount of typing errors, space wasted, helping you to arrange code, and providing an easy way to avoid some common HTML mistakes (like a wrong sequence in closing tags).

Why write the attrib height thousands of times in HTML code? Wouldnt it be much easier to write h, instead?

And what about closing 5 tags with a single character, without spending time getting the correct sequence?

How does it work?

TRASHY is written in the form of a function which you must link to your php code. An alias is provided for each tag and each attribute.

Each time you need to write HTML code pass it as the argument of TRASHY function, using aliases for tags and quoting normal text with some special characters.
The function parses your code char by char and expands each alias by exchanging it with the corresponding tag.

Text which is quoted with special characters is not parsed but simply copied as normal text, instead.

TRASHY keeps track of the tags you open step-by-step, so when you need to close a tag you only need to use 1 standard-close-tag character, and TRASHY closes the last opened tag(s) for you.

TRASHY uses a map of parent/child tag dependencies, created from the W3C strict HTML 4.01 Document Type Declaration. By using this map it can only expand allowed tags and help you to write valid HTML code. Aliases which lead to an incorrect sequence are ignored.

TRASHY project can be used and reused many times all over your php code. Tag history is stored in a global array, so you can close the function when you need to add some php code and then reopen a new TRASHY session to go on with HTML code just from the same point you left before.

TRASHY lets you attach all the attributes (and values) you need to each tag using special attribute-aliases.

TRASHY ignores spaces, tabs, CarriageReturn and LineFeed characters and lets you use them to arrange and indent your code in the same way as normal HTML, to make it ordered and more readable.
You can also add comments to your TRASHY code.

TRASHY can also help you to reduce the size of your php code (to 2/3rds of the equivalent HTML space). Also TRASHY produces compact HTML, with no spaces, no tabs, no CR or LF characters.

MyProfi project is a command line tool that parses mysql query log and outputs statistics of most frequently used queries, sorting them by number of times they appear in a log file. The similar queries are groupped together.
Thus, select id from user where login="admin" and select id from user where login=root become select id from user where login={} - the variable parts of queries are replaced with {} markers, this make statistics analysis as easy as revewing the top of most frequently occured queries patterns.
When developing an application one can hardly predict, which of the sql queries will run the most often, and which less often. The most popular queries are to be the first candidates for optimisation, fine tuning and polishing. By optimizing the most frequenly run queries the developer may achieve significant performance gain for overall system. By reviewing the statistics of MyProfi output its becomes too easy to extract those queries to start optimizing db by adding indexes, reconsidering database structure, etc.
Main features:
Removing unsignificant variable data
- Usually applications run similar queries against database, but using different variable parameters in them. For example, fetch some data by its ID number in a table. What we want is to know, how frequently this query was executed at all. By removing the variable data from all queries we can then group them and count how many times they appear in the log file. Thus, from two queries SELECT NAME FROM USER WHERE ID=223 and SELECT NAME FROM USER WHERE ID=223 we will get one pattern SELECT NAME FROM USER WHERE ID={} two times.
- As there may be variable data of different types we also wish to remove quoted strings (considering all possible escaping techniques), multiline and single line comments, unsignificant whitespaces, siquential variables like ID IN (1 ,2 ,3), etc.
Queries ordered by popularity
- Thats exactly the reason, why this utility has been developed - to know, which queries are the most frequently run on database server. The more popular the query is, the more performance may be gained by optimizing it.
Additional statistics
- For slow query formats there are available additional options to use for sorting by a different then number of queries criteria. As slow query log provides the information for each query about the time it was running, the time it was locked, the number of rows totally examined and finally returned. MyProfi allowes to sort the statistics by any of these field, and even by maximum, total or average numbers for each pattern.
Statistics by query type
- Query type statistics is sometimes useful for appropriate database server configuration and tuning. For example, if UPDATE queries are the most frequently run against database, a developer may consider restructurizing tables to reduce the use of indexes, as too many indexes in tables make its update slower. Or otherwise, if SELECT queries are popular, it may be a reason to allocate more memory buffer space, etc.
Different input formas support
- MyProfi understands several input file formats. Beside general query log format, slow query log format is also supported.
- As of version 5.1.x of MySQL server, both the general and slow query logs may be configured to be writen to mysql system table. By setting an appropriate option in MyProfi or providing input file with .csv extension we can tell the parser to treat input files as csv formatted.
- Moreover, for slow query log you can output an additional statistics.
Stream parsing
- No matter how huge your input file is, the parser will never load whole content into memory, but reads the file chunk by chunk (though, you might be going to wait for "some time" while this huge file is being processed).
Custom queries filtering
- You can choose to output statistics only for certain type of queries: SELECT, UPDATE, DELETE, etc. This may be useful, for instance, when you are going to check the most popular queries execution plan using EXPLAIN. In this case non-SELECT queries will be just useless.
Support for top N queries
- Output only first N patters in sorted statistics.

PTM is a Perl/HTML hybrid. An inline development language for those that need a bit more power behind the scenes.
But more than that, it allows developers to harness Perls ability to manipulate strings of text and iterate loops many times faster than other languages on the market without the need to sacrifice development time to complex print, split, and join statements.
Additionally, PTM wraps many variables common to PHP to ease the transition between PTM and PHP when switching back and forth.
PTM was not created to replace PHP or ASP. PTM project was designed to be a complement to them. Where one fails another picks up the slack. In the world of dynamic design we need all the tools in our toolbox to get the job done. PTM is the raw power tool youve been missing.
Enhancements:
- A few functions flagged by the testers have been fixed or have had minor changes in functionality made to them, and there are two major security enhancements that have been put into place.
- A couple new base functionality functions have been added.
- A new module (RSS20) has been added that allows for simple node-based parsing of RSS 2.0 compatible XML feeds both over the Internet and stored in local files.
- The .htaccess file has been shortened to provide less overhead in Standalone/Emulation installation mode, and the installation process has been simplified.

mylvmbackup project is a Perl script for quickly creating backups of MySQL servers data files. To perform a backup, mylvmbackup obtains a read lock on all tables and flushes all server caches to disk, makes an LVM snapshot of the volume containing the MySQL data directory, and unlocks the tables again. The snapshot process takes only a small amount of time. When it is done, the server can continue normal operations, while the actual file backup proceeds.
The LVM snapshot is mounted to a temporary directory and all data is backed up using the tar program. The archive file is created using a name of the form backup-YYYYMMDD_hhmmss_mysql.tar.gz, where YYYY, MM, DD, hh, mm, and ss represent the year, month, day, hour, minute, and second of the time at which the backup occurred. The prefix backup and the date format can be modified. The use of timestamped archive names allows you to run mylvmbackup many times without danger of rewriting old archives.
It is necessary to run mylvmbackup on the same host where the MySQL server runs. If your MySQL daemon is not listening on localhost, or using the default socket location, you must specify --host or --socket. Even though mylvmbackup communicates with the server through a normal client connection to obtain the read lock and flush data, it makes the backup by accessing the file system directly. It is also necessary that the MySQL server data directory resides on an LVM volume. (It is, however, a good idea to do the LVM backup to a different partition than the one where the data directory resides. Otherwise, there is a good chance that LVM will run out of undo space for LVM snapshot maintenance and the backup will fail.)
The user who invokes mylvmbackup must have sufficient filesystem permissions to create the LVM snapshot and mount it. This includes read/write access to the backup directory.
For proper operation mylvmbackup requires that Perl as well as the DBI and DBD::mysql modules. In addition, it uses several other programs: /bin/date to construct the archive filename, tar to back up data, LVM utilities to create and remove the LVM snapshot, and the system utilities mount and umount.
Enhancements:
- The "--innodb-recover" option was added, which provides an option to run InnoDB recovery on LVM2 snapshots (which provide write access to the device) prior to creating the backup archive.
- This speeds up resuming a MySQL instance from a restored backup.
- A bug with the default value handling for command line options was fixed. In version 0.4, if a config file was specified, default values in the script were all changed to blank.
- This means that the config file had to supply values for every variable instead of just the values that need to be changed from default.

Rubyripper is a secure audio-cd ripper for linux.

Through multiple times ripping the same track and correcting any differences Rubyripper tries to deliver a secure rip.