Free automagically software for linux

Apache::TestUtil Perl module contains utility functions for writing tests.

SYNOPSIS

use Apache::Test;
use Apache::TestUtil;

ok t_cmp("foo", "foo", "sanity check");
t_write_file("filename", @content);
my $fh = t_open_file($filename);
t_mkdir("/foo/bar");
t_rmtree("/foo/bar");
t_is_equal($a, $b);

Apache::TestUtil automatically exports a number of functions useful in writing tests.

All the files and directories created using the functions from this package will be automatically destroyed at the end of the program execution (via END block). You should not use these functions other than from within tests which should cleanup all the created directories and files at the end of the test.

FUNCTIONS

t_cmp()
t_cmp($received, $expected, $comment);
t_cmp() prints the values of $comment, $expected and $received. e.g.:
t_cmp(1, 1, "1 == 1?");
prints:
# testing : 1 == 1?
# expected: 1
# received: 1

then it returns the result of comparison of the $expected and the $received variables. Usually, the return value of this function is fed directly to the ok() function, like this:

ok t_cmp(1, 1, "1 == 1?");

the third argument ($comment) is optional, mostly useful for telling what the comparison is trying to do.

It is valid to use undef as an expected value. Therefore:

my $foo;
t_cmp(undef, $foo, "undef == undef?");

will return a true value.

You can compare any two data-structures with t_cmp(). Just make sure that if you pass non-scalars, you have to pass their references. The datastructures can be deeply nested. For example you can compare:

t_cmp({1 => [2..3,{5..8}], 4 => [5..6]},
{1 => [2..3,{5..8}], 4 => [5..6]},
"hash of array of hashes");

You can also compare the second argument against the first as a regex. Use the qr// function in the second argument. For example:

t_cmp("abcd", qr/^abc/, "regex compare");
will do:
"abcd" =~ /^abc/;

This function is exported by default.

t_filepath_cmp()

This function is used to compare two filepaths via t_cmp(). For non-Win32, it simply uses t_cmp() for the comparison, but for Win32, Win32::GetLongPathName() is invoked to convert the first two arguments to their DOS long pathname. This is useful when there is a possibility the two paths being compared are not both represented by their long or short pathname.

This function is exported by default.

t_debug()
t_debug("testing feature foo");
t_debug("test", [1..3], 5, {a=>[1..5]});

t_debug() prints out any datastructure while prepending # at the beginning of each line, to make the debug printouts comply with Test::Harnesss requirements. This function should be always used for debug prints, since if in the future the debug printing will change (e.g. redirected into a file) your tests wont need to be changed.

the special global variable $Apache::TestUtil::DEBUG_OUTPUT can be used to redirect the output from t_debug() and related calls such as t_write_file(). for example, from a server-side test you would probably need to redirect it to STDERR:

sub handler {
plan $r, tests => 1;

local $Apache::TestUtil::DEBUG_OUTPUT = *STDERR;

t_write_file(/tmp/foo, bar);
...
}

left to its own devices, t_debug() will collide with the standard HTTP protocol during server-side tests, resulting in a situation both confusing difficult to debug. but STDOUT is left as the default, since you probably dont want debug output under normal circumstances unless running under verbose mode.

This function is exported by default.

t_write_file()
t_write_file($filename, @lines);

t_write_file() creates a new file at $filename or overwrites the existing file with the content passed in @lines. If only the $filename is passed, an empty file will be created.

If parent directories of $filename dont exist they will be automagically created.

The generated file will be automatically deleted at the end of the programs execution.

This function is exported by default.

t_append_file()
t_append_file($filename, @lines);

t_append_file() is similar to t_write_file(), but it doesnt clobber existing files and appends @lines to the end of the file. If the file doesnt exist it will create it.

If parent directories of $filename dont exist they will be automagically created.

The generated file will be registered to be automatically deleted at the end of the programs execution, only if the file was created by t_append_file().

This function is exported by default.

t_write_shell_script()
Apache::TestUtil::t_write_shell_script($filename, @lines);

Similar to t_write_file() but creates a portable shell/batch script. The created filename is constructed from $filename and an appropriate extension automatically selected according to the platform the code is running under.

It returns the extension of the created file.

t_write_perl_script()
Apache::TestUtil::t_write_perl_script($filename, @lines);

Similar to t_write_file() but creates a executable Perl script with correctly set shebang line.

t_open_file()
my $fh = t_open_file($filename);

t_open_file() opens a file $filename for writing and returns the file handle to the opened file.

If parent directories of $filename dont exist they will be automagically created.

The generated file will be automatically deleted at the end of the programs execution.

This function is exported by default.

t_mkdir()
t_mkdir($dirname);

t_mkdir() creates a directory $dirname. The operation will fail if the parent directory doesnt exist.

If parent directories of $dirname dont exist they will be automagically created.

The generated directory will be automatically deleted at the end of the programs execution.

This function is exported by default.

t_rmtree()
t_rmtree(@dirs);
t_rmtree() deletes the whole directories trees passed in @dirs.

This function is exported by default.

t_chown()
Apache::TestUtil::t_chown($file);

Change ownership of $file to the tests User/Group. This function is noop on platforms where chown(2) is unsupported (e.g. Win32).

t_is_equal()
t_is_equal($a, $b);

t_is_equal() compares any two datastructures and returns 1 if they are exactly the same, otherwise 0. The datastructures can be nested hashes, arrays, scalars, undefs or a combination of any of these. See t_cmp() for an example.

If $b is a regex reference, the regex comparison $a =~ $b is performed. For example:

t_is_equal($server_version, qr{^Apache});

If comparing non-scalars make sure to pass the references to the datastructures.

This function is exported by default.

t_server_log_error_is_expected()

If the handlers execution results in an error or a warning logged to the error_log file which is expected, its a good idea to have a disclaimer printed before the error itself, so one can tell real problems with tests from expected errors. For example when testing how the package behaves under error conditions the error_log file might be loaded with errors, most of which are expected.

For example if a handler is about to generate a run-time error, this function can be used as:

use Apache::TestUtil;
...
sub handler {
my $r = shift;
...
t_server_log_error_is_expected();
die "failed because ...";
}

After running this handler the error_log file will include:

*** The following error entry is expected and harmless ***
[Tue Apr 01 14:00:21 2003] [error] failed because ...

When more than one entry is expected, an optional numerical argument, indicating how many entries to expect, can be passed. For example:

t_server_log_error_is_expected(2);

will generate:

*** The following 2 error entries are expected and harmless ***

If the error is generated at compile time, the logging must be done in the BEGIN block at the very beginning of the file:

BEGIN {
use Apache::TestUtil;
t_server_log_error_is_expected();
}
use DOES_NOT_exist;

After attempting to run this handler the error_log file will include:

*** The following error entry is expected and harmless ***
[Tue Apr 01 14:04:49 2003] [error] Cant locate "DOES_NOT_exist.pm"
in @INC (@INC contains: ...

Also see t_server_log_warn_is_expected() which is similar but used for warnings.

This function is exported by default.

t_server_log_warn_is_expected()
t_server_log_warn_is_expected() generates a disclaimer for expected warnings.

See the explanation for t_server_log_error_is_expected() for more details.

This function is exported by default.

t_client_log_error_is_expected()
t_client_log_error_is_expected() generates a disclaimer for expected errors. But in contrast to t_server_log_error_is_expected() called by the client side of the script.

See the explanation for t_server_log_error_is_expected() for more details.

For example the following client script fails to find the handler:

use Apache::Test;
use Apache::TestUtil;
use Apache::TestRequest qw(GET);

plan tests => 1;

t_client_log_error_is_expected();
my $url = "/error_document/cannot_be_found";
my $res = GET($url);
ok t_cmp(404, $res->code, "test 404");

After running this test the error_log file will include an entry similar to the following snippet:

*** The following error entry is expected and harmless ***
[Tue Apr 01 14:02:55 2003] [error] [client 127.0.0.1]
File does not exist: /tmp/test/t/htdocs/error

When more than one entry is expected, an optional numerical argument, indicating how many entries to expect, can be passed. For example:

t_client_log_error_is_expected(2);

will generate:

*** The following 2 error entries are expected and harmless ***

This function is exported by default.

t_client_log_warn_is_expected()
t_client_log_warn_is_expected() generates a disclaimer for expected warnings on the client side.

See the explanation for t_client_log_error_is_expected() for more details.

This function is exported by default.

t_catfile(a, b, c)

This function is essentially File::Spec->catfile, but on Win32 will use Win32::GetLongpathName() to convert the result to a long path name (if the result is an absolute file). The function is not exported by default.

t_catfile_apache(a, b, c)

This function is essentially File::Spec::Unix->catfile, but on Win32 will use Win32::GetLongpathName() to convert the result to a long path name (if the result is an absolute file). It is useful when comparing something to that returned by Apache, which uses a Unix-style specification with forward slashes for directory separators. The function is not exported by default.

t_start_error_log_watch(), t_finish_error_log_watch()

This pair of functions provides an easy interface for checking the presence or absense of any particular message or messages in the httpd error_log that were generated by the httpd daemon as part of a test suite. It is likely, that you should proceed this with a call to one of the t_*_is_expected() functions.

t_start_error_log_watch();
do_it;
ok grep {...} t_finish_error_log_watch()

Gallery Uploader is a Python script that can upload pictures to Web Gallery (only versions 2.0 or above).

Gallery Uploader supports multiple galleries. To do it so, you need to save URL, User and Password using the –save option, passing a name to the gallery. You can point to this gallery using the -G option. If there is only one gallery in the configuration, you won’t need the -G option, as GUP will automagically use that gallery.

Creating Albums

To create an album, you need the -c option. This option takes three parameters:

Parent album id: the id of the album where the new album will be created. There is an special album with id “0″, which is the root of all albums, but it is NOT the album you see when you open Web Gallery in the browser. To find this “first album”, you can use the –show-child=0 option;

Album name: it’s the name your gallery will have. In the web interface, it is the first field asked when creating an album. Internally, it is the directory name in the server where the pictures will be stored (so, invalid file names will cause GUP to fail);

Album title: it’s the visible part of the album, displayed on the page.

Also, note that there is three parameters and that space is used to split them. So, if you want to add spaces to your album name or album title, you need to enclose it by quotes, like -c 7 my_first_album “My First Album” (this will create an album named “My First Album”, stored as “my_first_album” in the server, under the album with the id “7″).

Uploading Images

To upload images, you need to create an album (using something like the above example) or using the -a option, passing the album id. Also, if you don’t need the picture in your computer after uploading, you can use the –delete option.

Nimages provides an image gallery script featuring themes and a Web-based installation.
Nimages is a simple image gallery script featuring a Web-based installtion and configuration (no editing of the script is needed).
Other features include MySQL support, automatic creation of thumbnails (if supported), themes, and ease of use and configuration.
Nimages is a complete rewrite of the JCS Image Display script.
Main features:
- A nifty web-based install automagically detects most options.
- An advanced and normal mode. Normal mode is for users who arent comfortable setting up and running scripts, and the advanced mode is for people who want a little more control.
- Only one file to mess with...Copy and Go!
- Complete editing of image information from withing the program.
- A system that lets authorized users log in and edit image info, add comments, and manipulate galleries.
- Uses MySQL if available.
- A comprehensive theme system.

Backup Monitor is an rsync backup front-end with a Web interface, which emails reports with an attached summary or logfile.
Backup Monitors configuration system is simple to use and can back up single servers or entire server farms from a single machine.
Custom email tags can be used to sort responses in your mail reader.
Enhancements:
- This release adds MySQL support for logging, cleans up email notifications, and fixes null additions and a whitespace issue.
- The installer [install.php] fills in most config fields automagically for you.
- Log size rotation is configurable.
- PID check has been updated, and now relies on Unix::PID cleanliness.
- RSYNC STDERR is now redirected for email notifications.

AFS::Command::VOS is a OO API to the AFS vos command.

$path_to_your_vos_binary,
);

my $vos = AFS::Command::VOS->new
(
localauth => 1,
encrypt => 1,
);

This module implements an OO API wrapper around the AFS vos command. The supported methods depend on the version of the vos binary used, and are determined automagically.

AFS::Command::BOS is a OO API to the AFS bos command.

SYNOPSIS

use AFS::Command::BOS;

my $bos = AFS::Command::BOS->new();

my $bos = AFS::Command::BOS->new
(
command => $path_to_your_bos_binary,
);

my $bos = AFS::Command::BOS->new
(
localauth => 1,
);

This module implements an OO API wrapper around the AFS bos command. The supported methods depend on the version of the bos binary used, and are determined automagically.

Mount ISO Image is an advanced script which allows to perform multiple operations with ISO, NRG (Nero Burning ROM), UDF (DVD), CUE/BIN, CCD/IMG/SUB (CloneCD), XDVDFS (XBOX) images.
Mount/unmount operations can be performed in two different ways: using kdesu or sudo. During the installation youll be offered to choose a variant to use.
Note: If you prefer to use sudo, you should first choose to "Setup sudo config" in installation menu.
Usage:
ISO9660 (CD) and UDF (DVD) images
Mount:
Right-click an ".ISO" file and choose "Actions -> Manage ISO -> Mount Image". Image file will be mounted to folder on Desktop, the corresponding folder will be opened and raised.
Unmount:
Right-click an ".ISO" file and choose "Actions -> Manage ISO -> Unmount Image". The corresponding folder will be removed from the desktop automagically.
Calculate MD5 sum:
Right-click an ".ISO" file, choose "Actions -> Manage ISO -> Calculate MD5 sum" and wait for completion - it may take several minutes for a standard 650 Mb image on a slow machine.
Create ISO/UDF image from directory:
Right-click a folder that you wish an ISO or UDF image to be created from and choose "Actions -> Manage ISO -> Create ISO (or UDF) image". Image will be created either in parent directory of this folder (if user is allowed to write there) or on the Desktop.
Warning: Check if you have enough free space on target partition before creating an ISO!
Create ISO/UDF image from CD/DVD drive:
Right-click any suitable directory (resulting file will be stored there), select "Actions -> Manage ISO -> Create ISO-image from CD-ROM" and select the name of ISO image in the filename selection dialog. If it suggests you put the resulting image on the Desktop instead of the selected directory, it means that current user has no permission to write in this directory.
Note: This feature requires a working CD/DVD drive
Warning: Check if you have enough free space on target partition before creating an ISO!
NRG (Nero Burning ROM) images
Mount:
Right-click an ".NRG" file and choose "Actions -> Manage NRG -> Mount Image". Image file will be mounted to folder on Desktop, the corresponding folder will be opened and raised.
Unmount:
Right-click an ".NRG" file and choose "Actions -> Manage NRG -> Unmount Image". The corresponding folder will be removed from the desktop automagically. You can also right-click this very folder on your to unmount.
Calculate MD5 sum:
Right-click an ".NRG" file, choose "Actions -> Manage NRG -> Calculate MD5 sum" and wait for completion - it may take several minutes for a standard 650 Mb image on a slow machine.
Convert NRG image to ISO
Right-click an ".NRG" file and choose "Actions -> Manage NRG -> Convert to ISO" to convert the image to a standard ISO.
Warning: Check if you have enough free space before converting!
CUE/BIN images
Mount:
Right-click a ".CUE" file and choose "Actions -> Manage CUE/BIN -> Mount Image". Image file will be mounted to folder on Desktop, the corresponding folder will be opened and raised.
Note: This feature requires the use of cdemu utility, available here: http://cdemu.sourceforge.net
If it is not installed on your system, you will need to compile it from source or find a suitable package.
Unmount:
Right-click a ".CUE" file and choose "Actions -> Manage CUE/BIN -> Unmount Image". The corresponding folder will be removed from the desktop automagically. You can also right-click this very folder on your to unmount.
Convert CUE/BIN image to ISO:
Right-click a ".CUE" file and choose "Actions -> Manage CUE/BIN -> Convert to ISO" to convert the image to a standard ISO.
Note: This feature requires bchunk utility, available here: http://he.fi/bchunk
If it is not installed on your system, you will need to compile it from source or find a suitable package.
Warning: Check if you have enough free space before converting!
CCD/IMG/SUB (CloneCD) images
Convert CloneCD image to ISO:
Right-click a ".CCD" file and choose "Actions -> Manage CloneCD -> Convert to ISO" to convert the image to a standard ISO.
Note: This feature requires ccd2iso utility, available here: http://sourceforge.net/projects/ccd2iso
If it is not installed on your system, you will need to compile it from source or find a suitable package.
Warning: Check if you have enough free space before converting!
XDVDFS (XBOX) images
Create XDVDFS image from directory:
Right-click a folder that you wish an XDVDFS image to be created from and choose "Actions -> Manage ISO -> Create XDVDFS image". Image will be created either in parent directory of this folder (if user is allowed to write there) or on the Desktop.
Note: This feature requires extract-xiso utility, available here
Warning: Check if you have enough free space on target partition before creating an ISO!
Installation:
tar -jxf mount-iso-image-0.9.tar.bz2
cd mount-iso-image-0.9
./install.sh
Please follow installer instructions
Translations:
- Czech (by Jozef Riha)
- Danish (by Kalna and BK)
- French (by MrYouP)
- German (by Xenonite and seraphyn)
- Hungarian (by Marcel Hilzinger and Vince Pinter)
- Italian (by marcosegato)
- Polish (by Lukasz Purgal)
- Portuguese/brazilean (by Groo and Dherik)
- Romanian (by Spoiala Cristian)
- Russian (by Jinjiru)
- Slovak (by Jozef Riha)
- Spanish (by mrthc)