Free linux archive manager software for linux

Linux Cluster Manager is a graphical tool for managing multiple Linux systems from a central location. Meant primarily for Beowulf style clusters, it has many useful features for general system administration and even some non Linux specific possibilities like block level imaging.
Imaging with LCM is quick and easy as each node has its IP and hostname changed ready for boot as an independant node preloaded with all of your applications. Using a file based image, items can be changed such as the target device, the file system capacity, or even the file system type. Imagine requiring a new partition on boot disks already filled across hundreds of machines. It is a simple property change, re-image the node(s), and you are ready to go.
Image creation can be done from a running system or LCM can remote power on a node through WOL, PXE boot it, collect an image, and power off the node when complete.
All operations are simple point and click, no command line options to remember (these are optional), or complicated setup.
Main features:
- Easy to use GUI for all operations
- Real time status information for all nodes
- Connect to individual nodes via a user specified protocol (ssh, rsh, rlogin ,etc)
- Report on running processes across the cluster
Imaging Features
- Imaged nodes have IP and hostname information changed automatically, just image and boot
- Block level system imaging (can be used for any x86 based operating system)
- File level system imaging
- Wake on LAN for imaging
- Preconfigured for PXE boot of clients
- Images can be customized - target device changed, file system size, file system type
Monitor Features
- Real time status monitoring for all nodes, CPU and Network
- Scrolling, scalable graphs
- View all nodes or a subset you are interested in
Scripting Features
- Run scripts across the cluster or on select nodes without a client agent
- Connects via a user selected protocol with secure authentication
- Command line or GUI interface
- Can be incorporated into external scripts

The Apache::FileManager module is a simple HTML file manager. It provides file manipulations such as cut, copy, paste, delete, rename, extract archive, create directory, create file, edit file, and upload files.
It also has the ability to rsync the server htdocs tree to another server with the click of a button.
Enhancements:
- prevented file edit screen from opening when cancel is clicked when creating new filenames
- fixed up documentation

Microsummary Manager provides an easily install, delete and manage your μSummary generators!

This extension provides an easy way to manage currently installed microsummary generators and install any you may have saved locally via the add-ons manager.

NTK manager provides a project and employees manager.

NTK manager is a client/server application for managing employees and the projects they work on in a fast and efficient manner.

Rsync Vault Manager is an archive manager that uses rsync to manage backups of multiple clients across multiple logical partitions (vaults).
Rsync Vault Manager has some features that some other rsync-based backup schemes lack, such as being written in C++, needing no scripts or other programs than rsync and any binaries on which rsync depends (such as SSH), the ability to manage multiple instances of rsync connections to separate clients in parallel, the ability to use multiple logical partitions (vaults) in a configurable fashion for purporses of redundancy and added reliability, and the use of hard links for files that have not changed from one archive to the next.
Rsync Vault Manager was developed on an x86 platform using Linux RedHat 9.0 w/ GCC 3.2.2 and an UltraSPARC platform using Solaris 8 w/ GCC 2.95.5.
Rsync Vault Manager uses GNU autoconf/automake scripts for compilation and installation.
Enhancements:
- Minor bugs fixed: a wildcard resolution bug, incorrect archive directory names, empty job IDs in reports, and this release checks that a vault is writable before running rsync.
- A vault locking option prevents multiple instances of rvm from using the same vault, there is a separate error logging level to be used when retrying an rsync command, and there is an option to delete old log files along with old archives.

Backup Manager is a command line backup tool for GNU/Linux, designed to help you make daily archives of your file system.
Backup Manager is written in bash and perl and it can make tar, tar.gz, tar.bz, and zip archives and can be run in a parallel mode with different configuration files.
Archives are kept for a given number of days and the upload system can use ftp or scp to transfer the generated archives to a list of remote hosts. The configuration file is very simple and basic and gettext is used for internationalization.
Main features:
- Make tar, tar.gz, tar.bz and zip archives.
- Automatically burn the archives on CDR/CDRW media.
- Logging to syslog is possible
- Perform MD5 checksums when burning data on CDR to be sure that archives arent corrupted.
- Backup MySQL databases with mysqldump
- Can be run in a parallel mode with different configuration files.
- Keep and purge all the archives for a given number of days.
- Upload the generated archives to remote hosts, either with ftp or scp.
- Provide two diffrent ways of naming the tarballs.
- Is completly integrated to the Debian environment.
- The Debian package uses debconf to provide a quick and easy setup.

Archive::Ar is a Perl interface for manipulating ar archives.

SYNOPSIS

use Archive::Ar;

my $ar = new Archive::Ar("./foo.ar");

$ar->add_data("newfile.txt","Some contents", $properties);

$ar->add_files("./bar.tar.gz", "bat.pl")
$ar->add_files(["./again.gz"]);

$ar->remove("file1", "file2");
$ar->remove(["file1", "file2");

my $filedata = $ar->get_content("bar.tar.gz");

my @files = $ar->list_files();
$ar->read("foo.deb");

$ar->write("outbound.ar");

$ar->DEBUG();

Archive::Ar is a pure-perl way to handle standard ar archives.

This is useful if you have those types of old archives on the system, but it is also useful because .deb packages for the Debian GNU/Linux distribution are ar archives. This is one building block in a future chain of modules to build, manipulate, extract, and test debian modules with no platform or architecture dependence.

You may notice that the API to Archive::Ar is similar to Archive::Tar, and this was done intentionally to keep similarity between the Archive::* modules

Class Methods
new()
new($filename)
new(*GLOB,$debug)

Returns a new Archive::Ar object. Without a filename or glob, it returns an empty object. If passed a filename as a scalar or in a GLOB, it will attempt to populate from either of those sources. If it fails, you will receive undef, instead of an object reference.

This also can take a second optional debugging parameter. This acts exactly as if DEBUG() is called on the object before it is returned. If you have a new() that keeps failing, this should help.
read($filename)
read(*GLOB);

This reads a new file into the object, removing any ar archive already represented in the object. Any calls to DEBUG() are not lost by reading in a new file. Returns the number of bytes read, undef on failure.

read_memory($data)

This read information from the first parameter, and attempts to parse and treat it like an ar archive. Like read(), it will wipe out whatever you have in the object and replace it with the contents of the new archive, even if it fails. Returns the number of bytes read (processed) if successful, undef otherwise.

list_files()
This lists the files contained inside of the archive by filename, as an array.
add_files("filename1", "filename2")
add_files(["filename1", "filename2"])

Takes an array or an arrayref of filenames to add to the ar archive, in order. The filenames can be paths to files, in which case the path information is stripped off. Filenames longer than 16 characters are truncated when written to disk in the format, so keep that in mind when adding files.

Due to the nature of the ar archive format, add_files() will store the uid, gid, mode, size, and creation date of the file as returned by stat();

add_files() returns the number of files successfully added, or undef on failure.
add_data("filename", $filedata)

Takes an filename and a set of data to represent it. Unlike add_files, add_data is a virtual add, and does not require data on disk to be present. The data is a hash that looks like:

$filedata = {
"data" => $data,
"uid" => $uid, #defaults to zero
"gid" => $gid, #defaults to zero
"date" => $date, #date in epoch seconds. Defaults to now.
"mode" => $mode, #defaults to "100644";
}

You cannot add_data over another file however. This returns the file length in bytes if it is successful, undef otherwise.

write()
write("filename.ar")

This method will return the data as an .ar archive, or will write to the filename present if specified. If given a filename, write() will return the length of the file written, in bytes, or undef on failure. If the filename already exists, it will overwrite that file.
get_content("filename")

This returns a hash with the file content in it, including the data that the file would naturally contain. If the file does not exist or no filename is given, this returns undef. On success, a hash is returned with the following keys:

name - The file name
date - The file date (in epoch seconds)
uid - The uid of the file
gid - The gid of the file
mode - The mode permissions
size - The size (in bytes) of the file
data - The contained data
remove("filename1", "filename2")
remove(["filename1", "filename2"])

The remove method takes a filenames as a list or as an arrayref, and removes them, one at a time, from the Archive::Ar object. This returns the number of files successfully removed from the archive.

DEBUG()

This method turns on debugging. Optionally this can be done by passing in a value as the second parameter to new. While verbosity is enabled, Archive::Ar will toss a warn() if there is a suspicious condition or other problem while proceeding. This should help iron out any problems you have while using the module.

Disk Manager project is a simple filesystem configurator that allow you to:
- Automaticly detect new partitions at startup.
- Fully manage configuration of filesystem.
- Enable/disable write support for NTFS (need ntfs-3g installed).