how to rename multiple files
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 11477
IO::Multiplex 1.08
IO::Multiplex is a Perl module that can manage IO on many file handles. more>>
IO::Multiplex is a Perl module that can manage IO on many file handles.
SYNOPSIS
use IO::Multiplex;
my $mux = new IO::Multiplex;
$mux->add($fh1);
$mux->add(*FH2);
$mux->set_callback_object(...);
$mux->listen($server_socket);
$mux->loop;
sub mux_input {
...
}
IO::Multiplex is designed to take the effort out of managing multiple file handles. It is essentially a really fancy front end to the select system call. In addition to maintaining the select loop, it buffers all input and output to/from the file handles. It can also accept incoming connections on one or more listen sockets.
It is object oriented in design, and will notify you of significant events by calling methods on an object that you supply. If you are not using objects, you can simply supply __PACKAGE__ instead of an object reference.
You may have one callback object registered for each file handle, or one global one. Possibly both -- the per-file handle callback object will be used instead of the global one.
Each file handle may also have a timer associated with it. A callback function is called when the timer expires.
<<lessSYNOPSIS
use IO::Multiplex;
my $mux = new IO::Multiplex;
$mux->add($fh1);
$mux->add(*FH2);
$mux->set_callback_object(...);
$mux->listen($server_socket);
$mux->loop;
sub mux_input {
...
}
IO::Multiplex is designed to take the effort out of managing multiple file handles. It is essentially a really fancy front end to the select system call. In addition to maintaining the select loop, it buffers all input and output to/from the file handles. It can also accept incoming connections on one or more listen sockets.
It is object oriented in design, and will notify you of significant events by calling methods on an object that you supply. If you are not using objects, you can simply supply __PACKAGE__ instead of an object reference.
You may have one callback object registered for each file handle, or one global one. Possibly both -- the per-file handle callback object will be used instead of the global one.
Each file handle may also have a timer associated with it. A callback function is called when the timer expires.
Download (0.014MB)
Added: 2007-01-02 License: Perl Artistic License Price:
1025 downloads
AVI TV Episode File Resizer 1.0
AVI TV Episode File Resizer was made to fit (resize the file) multiple Xvid TV episodes (entire season) on a single DVD. more>>
AVI TV Episode File Resizer script is not for multiple MOVIE files (only TV) however it can do SINGLE MOVIE files quite nicely. The project was designed to help me fit (resize the file) multiple Xvid TV episodes (entire season) on a single DVD. Most of the time a TV series is almost exactly the same hours, mins, secs.
That enables this script to set the video bitrate the same for every file (episode) being processed to get the desired file size. The calculation is based on the hours, mins, seconds and the desired file size you want. If you correctly enter the time you will end up with a file size VERY close to the value you entered. The episodes will likley vary about 10 secs or so. Try to average that out when you select the episode time
The new files will have the EXACT same name as the old files so the input and output cannot be in the same DIRECTORY.
The "input files" selector can select multiple files so you can encode one or many files.
If you select an entire season (about 25 episodes) of files it could take quite a few hours to complete. The progress bar updates AFTER the completion of the first file and after every file there after. The current file being processed is displayed in the bottom status bar.
Transcode single pass is used to REencode the files.
Each file will be REencoded with MP3 audio bitrate of 96 kbps. The video is REencoded with the Xvid4 codec.
I used this script to go from 230MB to 175MB with good results. That saved me almost 1.4G for the season (25 episodes) and let me get it on a single DVD to play on my stand alone player.
You should try it with a single file first to check the quality and then do a batch job.
There are other tools to do this but this one can be setup and going in less than 1 min.
It takes almost 10 hours to do an entire season (25 episodes) at an episode time of 25 min 30 sec with a target file size of 171MB (ends up being about 174.8MB)
<<lessThat enables this script to set the video bitrate the same for every file (episode) being processed to get the desired file size. The calculation is based on the hours, mins, seconds and the desired file size you want. If you correctly enter the time you will end up with a file size VERY close to the value you entered. The episodes will likley vary about 10 secs or so. Try to average that out when you select the episode time
The new files will have the EXACT same name as the old files so the input and output cannot be in the same DIRECTORY.
The "input files" selector can select multiple files so you can encode one or many files.
If you select an entire season (about 25 episodes) of files it could take quite a few hours to complete. The progress bar updates AFTER the completion of the first file and after every file there after. The current file being processed is displayed in the bottom status bar.
Transcode single pass is used to REencode the files.
Each file will be REencoded with MP3 audio bitrate of 96 kbps. The video is REencoded with the Xvid4 codec.
I used this script to go from 230MB to 175MB with good results. That saved me almost 1.4G for the season (25 episodes) and let me get it on a single DVD to play on my stand alone player.
You should try it with a single file first to check the quality and then do a batch job.
There are other tools to do this but this one can be setup and going in less than 1 min.
It takes almost 10 hours to do an entire season (25 episodes) at an episode time of 25 min 30 sec with a target file size of 171MB (ends up being about 174.8MB)
Download (0.011MB)
Added: 2007-04-02 License: GPL (GNU General Public License) Price:
950 downloads
PhotoFS snapshot-84
PhotoFS provides a Web- and shell-based photo album based on ReiserFS concepts. more>>
PhotoFS provides a Web- and shell-based photo album based on ReiserFS concepts.
PhotoFS is a Web-based photo album or image gallery, based on the files-as-directories and attributes-as-files concepts at the core of the ReiserFS 4 filesystem.
It does not require ReiserFS 4, but is much more efficient on that system than on others. It does many of the same things as other Web galleries, at least as far as the basics go.
What makes it different is its use of the filesystem instead of a database. It allows you to use regular unix tools to access your photo collection.
It can handle very large collections, and also encourages multiple categories per file, deep category hierarchies, and batch processing.
Main features:
- Hierarchic categories
- Multiple categories per photo, plus "also in..." feature
- All data stored in the filesystem
- Browsable both on the web and from the command line
- Uses standard filesystem tools to access records
- Easy backup and replication with tar, rsync, etc...
- Uses no special file formats; data is stored in many small files instead of a database or several large files.
- works best with reiserfs v4, but is compatible with any filesystem
- Insert many photos at once from the command line
- Clean URLs; simple directory structure and no huge ?argument=foo lists
- Secure web interface
- Access control for web use: per user, per file, per category
- Non-public files cannot be viewed by the wrong users, even if those users know where to look.
- Restricted files are completely invisible to anyone not authorized to view them.
- Metadata:
- Description: Yes. HTML allowed. Can be edited with any text editor.
- Extended Description: Yes.
- Title: No. Use the description or filename.
- Keywords: No. (irrelevant; use the category system)
- People: No. (irrelevant; use the category system)
- Event: No. (irrelevant; use the category system)
- Date: Yes, for now. May be removed.
- Photographer: No, but may be added.
- No SQL database required
- Fast! Handles many, many thousands of files easily
- Auto thumbnail creation and caching (manual creation supported too)
- Auto-creates medium-sized previews when appropriate (manual creation supported too)
- Holds any type of file, not just images
- Integrates easily into php template systems with header/footer hooks
<<lessPhotoFS is a Web-based photo album or image gallery, based on the files-as-directories and attributes-as-files concepts at the core of the ReiserFS 4 filesystem.
It does not require ReiserFS 4, but is much more efficient on that system than on others. It does many of the same things as other Web galleries, at least as far as the basics go.
What makes it different is its use of the filesystem instead of a database. It allows you to use regular unix tools to access your photo collection.
It can handle very large collections, and also encourages multiple categories per file, deep category hierarchies, and batch processing.
Main features:
- Hierarchic categories
- Multiple categories per photo, plus "also in..." feature
- All data stored in the filesystem
- Browsable both on the web and from the command line
- Uses standard filesystem tools to access records
- Easy backup and replication with tar, rsync, etc...
- Uses no special file formats; data is stored in many small files instead of a database or several large files.
- works best with reiserfs v4, but is compatible with any filesystem
- Insert many photos at once from the command line
- Clean URLs; simple directory structure and no huge ?argument=foo lists
- Secure web interface
- Access control for web use: per user, per file, per category
- Non-public files cannot be viewed by the wrong users, even if those users know where to look.
- Restricted files are completely invisible to anyone not authorized to view them.
- Metadata:
- Description: Yes. HTML allowed. Can be edited with any text editor.
- Extended Description: Yes.
- Title: No. Use the description or filename.
- Keywords: No. (irrelevant; use the category system)
- People: No. (irrelevant; use the category system)
- Event: No. (irrelevant; use the category system)
- Date: Yes, for now. May be removed.
- Photographer: No, but may be added.
- No SQL database required
- Fast! Handles many, many thousands of files easily
- Auto thumbnail creation and caching (manual creation supported too)
- Auto-creates medium-sized previews when appropriate (manual creation supported too)
- Holds any type of file, not just images
- Integrates easily into php template systems with header/footer hooks
Download (0.11MB)
Added: 2007-02-07 License: GPL (GNU General Public License) Price:
989 downloads
ConfigReader::Simple 1.25
ConfigReader::Simple is a simple configuration file parser. more>>
ConfigReader::Simple is a simple configuration file parser.
SYNOPSIS
use ConfigReader::Simple;
# parse one file
$config = ConfigReader::Simple->new("configrc", [qw(Foo Bar Baz Quux)]);
# parse multiple files, in order
$config = ConfigReader::Simple->new_multiple(
Files => [ "global", "configrc" ],
Keys => [qw(Foo Bar Baz Quux)]
);
my @directives = $config->directives;
$config->get( "Foo" );
if( $config->exists( "Bar" ) )
{
print "Bar was in the config filen";
}
# copy an object to play with it separately
my $clone = $config->clone;
# only affects clone
$clone->set( "Foo", "Buster" );
# save the config to a single file
$clone->save( "configrc" )
# save the config to a single file, but only with
# certain directives
$clone->save( "configrc" => [qw(Foo Bar)] )
# save to multiple configuration files
$clone->save(
"configrc" => [qw(Foo Bar)],
"global" => [qw(Baz Quux)],
);
ConfigReader::Simple reads and parses simple configuration files. It is designed to be smaller and simpler than the ConfigReader module and is more suited to simple configuration files.
<<lessSYNOPSIS
use ConfigReader::Simple;
# parse one file
$config = ConfigReader::Simple->new("configrc", [qw(Foo Bar Baz Quux)]);
# parse multiple files, in order
$config = ConfigReader::Simple->new_multiple(
Files => [ "global", "configrc" ],
Keys => [qw(Foo Bar Baz Quux)]
);
my @directives = $config->directives;
$config->get( "Foo" );
if( $config->exists( "Bar" ) )
{
print "Bar was in the config filen";
}
# copy an object to play with it separately
my $clone = $config->clone;
# only affects clone
$clone->set( "Foo", "Buster" );
# save the config to a single file
$clone->save( "configrc" )
# save the config to a single file, but only with
# certain directives
$clone->save( "configrc" => [qw(Foo Bar)] )
# save to multiple configuration files
$clone->save(
"configrc" => [qw(Foo Bar)],
"global" => [qw(Baz Quux)],
);
ConfigReader::Simple reads and parses simple configuration files. It is designed to be smaller and simpler than the ConfigReader module and is more suited to simple configuration files.
Download (0.011MB)
Added: 2007-04-12 License: Perl Artistic License Price:
934 downloads
DV Video Assembler 0.93
DV Video Assembler allows you to append multiple Sony DV files. more>>
This application is particularly useful for owners of digital DV video cameras and other people who use the Sony DV video format for high quality video production.
DV Assembler allows you to append multiple Sony DV files with nice looking transition effects for both audio and video. Multiple transition effects are supported, like cross-fade, zoom, blur and a flash effect.
I created DV Assembler because there are no user friendly video editing applications for Linux. Yes, Kino is promising, but its user interface is still a mess and development is slow.
DV Assembler only touches the head and tail parts of the original video files that are needed to create the transition effects. The rest of the video is left untouched, which means zero quality loss.
DV Assembler can also be used to generate video editing scripts that can be run without KDE and Kommander.
<<lessDV Assembler allows you to append multiple Sony DV files with nice looking transition effects for both audio and video. Multiple transition effects are supported, like cross-fade, zoom, blur and a flash effect.
I created DV Assembler because there are no user friendly video editing applications for Linux. Yes, Kino is promising, but its user interface is still a mess and development is slow.
DV Assembler only touches the head and tail parts of the original video files that are needed to create the transition effects. The rest of the video is left untouched, which means zero quality loss.
DV Assembler can also be used to generate video editing scripts that can be run without KDE and Kommander.
Download (0.023MB)
Added: 2005-09-21 License: GPL (GNU General Public License) Price:
1498 downloads
MultiRecode 2.0
MultiRecode is a user interface for util recode to recode WWW from one coding to the other coding. more>>
MultiRecode is a user interface for util recode to recode WWW from one coding to the other coding.
It dont change metatag in files. This UI works with list of files for multiple recoding. You need recode in your PC installed.
<<lessIt dont change metatag in files. This UI works with list of files for multiple recoding. You need recode in your PC installed.
Download (0.061MB)
Added: 2006-07-25 License: Freeware Price:
1186 downloads
Thunar Media Tags Plugin 0.1.2
Thunar Media Tags Plugin (thunar-media-tags-plugin) adds special features for media files to the Thunar File Manager. more>>
Thunar Media Tags Plugin (thunar-media-tags-plugin) adds special features for media files to the Thunar File Manager.
Main features:
- a so-called bulk renamer, which allows users to rename multiple audio files at once, based on their tags (e.g. ID3 or OGG/Vorbis),
- a special media file page for the file properties dialog, which displays detailed information about quality, length etc.,
- and finally, an audio tag editor which is reachable from both, renamer and the properties page.
<<lessMain features:
- a so-called bulk renamer, which allows users to rename multiple audio files at once, based on their tags (e.g. ID3 or OGG/Vorbis),
- a special media file page for the file properties dialog, which displays detailed information about quality, length etc.,
- and finally, an audio tag editor which is reachable from both, renamer and the properties page.
Download (0.27MB)
Added: 2007-03-07 License: GPL (GNU General Public License) Price:
963 downloads
Tie::FieldVals 0.40
Tie::FieldVals is an array tie for a file of enhanced Field:Value data. more>>
Tie::FieldVals is an array tie for a file of enhanced Field:Value data.
SYNOPSIS
use Tie::FieldVals;
use Tie::FieldVals::Row;
# tie the array
my @records;
my $recs_obj = tie @records, Tie::FieldVals, datafile=>$datafile;
# object methods
my @field_names = $recs_obj->field_names();
This is a Tie object to map the records in an enhanced Field:Value data file into an array. Each file has multiple records, each record has its values defined by a Field:Value pair, with the enhancements that (a) the Value part can extend over more than one line (because the Field names are predefined) and (b) Fields can have multiple values by repeating the Field:Value part for a given field.
Because of its use of the Tie::File module, access to each record is reasonably fast. The Tie::File module also ensures that (a) the whole file doesnt have to be read into memory (b) record changes are written to the file straight away (c) record changes dont require the whole file to be rewritten, just the part of the file after the change.
The advantage of this setup is that one can have useful data files which are plain text, human readable, human editable, and at the same time able to be accessed faster than using XML (I know, I wrote a version of my reporting software using XML data, and even the fastest XML parsers werent as fast as this setup, once there were a reasonable number of records). This also has advantages over a simpler setup where values are given one per line with no indication of what value belongs to what field; the problems with that is that it is harder to fix corrupted data by hand, and it is harder to add new fields, and one cant have multi-line data.
It is likewise better than a CSV (Comma-Separated Values) file, because again, with a CSV file, the data is positional and therefore harder to fix and harder to change, and again one cant have multi-line data.
This module is both better and worse than file-oriented databases like DB_File and its variants and extensions (such as MLDBM). This module does not require that each record have a unique key, and the fact that a DBM file is binary makes it not only less correctable, but also less portable. On the downside, this module isnt as fast.
Naturally, if ones data needs are more complex, it is probably better to use a fully-fledged database; this is oriented towards those who dont wish to have the overhead of setting up and maintaining a relational database server, and wish to use something more straightforward.
This comes bundled with other support modules, such as the Tie::FieldVals::Row module. The Tie::FieldVals::Select module is for selecting and sorting a sub-set from a Tie::FieldVals array, and the Tie::FieldVals::Join is a very simple method of joining two files on a common field.
This distribution includes the fv2xml script, which converts a Tie::FieldVals data file into an XML file, and xml2fv which converts an XML file into a Tie::FieldVals data file.
<<lessSYNOPSIS
use Tie::FieldVals;
use Tie::FieldVals::Row;
# tie the array
my @records;
my $recs_obj = tie @records, Tie::FieldVals, datafile=>$datafile;
# object methods
my @field_names = $recs_obj->field_names();
This is a Tie object to map the records in an enhanced Field:Value data file into an array. Each file has multiple records, each record has its values defined by a Field:Value pair, with the enhancements that (a) the Value part can extend over more than one line (because the Field names are predefined) and (b) Fields can have multiple values by repeating the Field:Value part for a given field.
Because of its use of the Tie::File module, access to each record is reasonably fast. The Tie::File module also ensures that (a) the whole file doesnt have to be read into memory (b) record changes are written to the file straight away (c) record changes dont require the whole file to be rewritten, just the part of the file after the change.
The advantage of this setup is that one can have useful data files which are plain text, human readable, human editable, and at the same time able to be accessed faster than using XML (I know, I wrote a version of my reporting software using XML data, and even the fastest XML parsers werent as fast as this setup, once there were a reasonable number of records). This also has advantages over a simpler setup where values are given one per line with no indication of what value belongs to what field; the problems with that is that it is harder to fix corrupted data by hand, and it is harder to add new fields, and one cant have multi-line data.
It is likewise better than a CSV (Comma-Separated Values) file, because again, with a CSV file, the data is positional and therefore harder to fix and harder to change, and again one cant have multi-line data.
This module is both better and worse than file-oriented databases like DB_File and its variants and extensions (such as MLDBM). This module does not require that each record have a unique key, and the fact that a DBM file is binary makes it not only less correctable, but also less portable. On the downside, this module isnt as fast.
Naturally, if ones data needs are more complex, it is probably better to use a fully-fledged database; this is oriented towards those who dont wish to have the overhead of setting up and maintaining a relational database server, and wish to use something more straightforward.
This comes bundled with other support modules, such as the Tie::FieldVals::Row module. The Tie::FieldVals::Select module is for selecting and sorting a sub-set from a Tie::FieldVals array, and the Tie::FieldVals::Join is a very simple method of joining two files on a common field.
This distribution includes the fv2xml script, which converts a Tie::FieldVals data file into an XML file, and xml2fv which converts an XML file into a Tie::FieldVals data file.
Download (0.053MB)
Added: 2007-08-21 License: Perl Artistic License Price:
794 downloads
Multistat 0.1
Multistat is designed to be a flexible log file parser for multiple game servers. more>>
Multistat is designed to be a flexible log file parser for multiple game servers.
Designed with an extensible plugin interface, it is able to process statistics for any game and output them in any format simply by the use of custom modules.
Currently modules for Halflife, Counterstrike Source, Unreal Tournament 2004, Call of Duty 1, Unreal Tournament, and HTML output are included.
<<lessDesigned with an extensible plugin interface, it is able to process statistics for any game and output them in any format simply by the use of custom modules.
Currently modules for Halflife, Counterstrike Source, Unreal Tournament 2004, Call of Duty 1, Unreal Tournament, and HTML output are included.
Download (0.20MB)
Added: 2006-04-27 License: GPL (GNU General Public License) Price:
1276 downloads
Easy PHP Upload 2.28
Easy PHP Upload is a PHP upload class that can be used to upload files with a client browser to a remote Web server. more>>
Easy PHP Upload class (the old name) can be used to upload files with a client browser to a remote webserver location.
The features in the first release are: file-extension check, maximum file- size limitation and a flexible error reporting system. The class is extremely easy to use and comes together with full working examples. Sinds the second version is it possible to upload multiple files.
Check the class file for all update information. The version 2.22 (and higher) is compatible with the PHP directive "register_globals=off". NEW functions for the multiple upload function: rename files and filename validation.
With the updated (ver. 2.25) photo upload extension its possible to upload photos (logos) and resize them to the maximum X and Y size.
Enhancements:
- Two more languages (for the messages) were added to the class: Brazilian Portuguese and Bulgarian.
- All translations (except de, nl, en, and fr) are stored in external files.
- The new function to create non-existing directories was not working for the photo upload extension and has been fixed.
- The check_dir() method is more flexible now and can be used for more locations.
- The process_image() method from the photo_upload extension was modified to use this check now.
<<lessThe features in the first release are: file-extension check, maximum file- size limitation and a flexible error reporting system. The class is extremely easy to use and comes together with full working examples. Sinds the second version is it possible to upload multiple files.
Check the class file for all update information. The version 2.22 (and higher) is compatible with the PHP directive "register_globals=off". NEW functions for the multiple upload function: rename files and filename validation.
With the updated (ver. 2.25) photo upload extension its possible to upload photos (logos) and resize them to the maximum X and Y size.
Enhancements:
- Two more languages (for the messages) were added to the class: Brazilian Portuguese and Bulgarian.
- All translations (except de, nl, en, and fr) are stored in external files.
- The new function to create non-existing directories was not working for the photo upload extension and has been fixed.
- The check_dir() method is more flexible now and can be used for more locations.
- The process_image() method from the photo_upload extension was modified to use this check now.
Download (0.013MB)
Added: 2006-01-26 License: GPL (GNU General Public License) Price:
1404 downloads
mp3 CUE cutter 0.4.0
mp3 CUE cutter cuts MP3 files according to a .cue file. more>>
mp3cue cuts an input MP3 file according to the information stored in a .cue file (for example multiple tracks of DJ mix), and writes the output to multiple MP3 files.
poc is a mp3 and ogg streamer supporting following protocols:
HTTP (mp3 and ogg)
RTP (RFC 2250) (mp3 only)
RTP (RFC 3119) (mp3 only)
homegrown FEC protocol (mp3 only)
It should work under any POSIX platform, and does not require any additional library. You need a C99 compiler though.
poc is still beta software, ipv6 and ogg support was not tested extensively.
poc includes mp3cue, a mp3 CUE cutter, and mp3cut, a mp3 command-line editing tool.
<<lesspoc is a mp3 and ogg streamer supporting following protocols:
HTTP (mp3 and ogg)
RTP (RFC 2250) (mp3 only)
RTP (RFC 3119) (mp3 only)
homegrown FEC protocol (mp3 only)
It should work under any POSIX platform, and does not require any additional library. You need a C99 compiler though.
poc is still beta software, ipv6 and ogg support was not tested extensively.
poc includes mp3cue, a mp3 CUE cutter, and mp3cut, a mp3 command-line editing tool.
Download (0.094MB)
Added: 2005-09-28 License: Freely Distributable Price:
979 downloads

PeaZip for Linux 2.1
Free archiver utility, open 7Z, ACE, PAQ, TAR, RAR, ZIP, encrypt and split files more>> PeaZip is an open source file and archive manager for 32 and 64 bit Windows (9x, 2000, XP, Vista) and Linux.
For both platforms it is available as installable or portable package, not needing installation.
Full support: 7Z, 7Z-sfx, ARC/WRC, BZ2/TBZ2, GZ/TGZ, PAQ/LPAQ, PEA, QUAD, split, TAR, UPX, ZIP.
Open, browse, extract, test: ACE, ARJ, CAB, CHM, COMPOUND (MSI, DOC, XLS, PPT), CPIO, ISO, Java (JAR, EAR, WAR), Linux (DEB, PET/PUP, RPM, SLP), LHA/LZH, LZMA, NSIS, OOo, PAK/PK3/PK4, RAR, SMZIP, U3P, WIM, XPI, Z/TZ.
Other features: robust file copy, split/join files, quick or secure file deletion, byte to byte compare files, checksum/hash files, system benchmark, generate random passwords and keyfiles.
PeaZip allows to: browse files and archives (with multiple inclusion and exclusion filters), create/extract multiple archives at once, save archives layout, save job definition as command line (to be inspected, or used in scripts), save job logs.
The user interface is skinnable for colors, transparence and icons.<<less
Download (5.47MB)
Added: 2009-04-24 License: Freeware Price: Free
182 downloads
Parallel Virtual File System 1.6.3
Parallel Virtual File System is a parallel file system for clusters of PCs more>>
The goal of the Parallel Virtual File System (PVFS) Project is to explore the design, implementation, and uses of parallel I/O. PVFS serves as both a platform for parallel I/O research as well as a production file system for the cluster computing community. PVFS is currently targeted at clusters of workstations, or Beowulfs.
The PVFS project is conducted jointly between The Parallel Architecture Research Laboratory at Clemson University and The Mathematics and Computer Science Division at Argonne National Laboratory.
Additional funding for the PVFS project comes from NASA Goddard Space Flight Center Code 930 and The National Computational Science Alliance through the National Science Foundations Partnerships for Advanced Computational Infrastructure.
Main features:
- Compatibility with existing binaries
- Ease of installation
- User-controlled striping of files across nodes
- Multiple interfaces, including a MPI-IO interface via ROMIO
- Utilizes commodity network and storage hardware
PVFS supports the UNIX I/O interface and allows existing UNIX I/O programs to use PVFS files without recompiling. The familiar UNIX file tools (ls, cp, rm, etc.) will all operate on PVFS files and directories as well. This is accomplished via a Linux kernel module which is provided as a separate package.
PVFS is easy to install. The Quick Start page describes how to set up a simple installation. Scripts and test applications are included to help with configuration, testing for correct operation, and performance evaluation.
PVFS stripes file data across multiple disks in different nodes in a cluster. By spreading out file data in this manner, larger files can be created, potential bandwidth is increased, and network bottlenecks are minimized. A 64-bit interface is implemented as well, allowing large (more than 2GB) files to be created and accessed.
Enhancements:
- fixes to build under redhat 2.4.20-20.9 kernel
- checks for missing headers on ancient 2.4 kernels
- removal of unused fields from metadata and control messages
- updated pvfsd rc file
- handle various combinations of redhat kernel patches
- fixes to kpvfsd that had previously been fixed in user space
- fix for sftp directory reading problems
- fix to avoid oopses on clients when bad errno values returned
- adjustments to deal wiht gcc 3.4.0 issues
- fixes to work with redhat 9
- fixes to compile kernel code for xx86_64
- updated logging intrastructure
- fixes to error reporting
- update of makefile in pvfs core
- fix to bug in pvfs_open.c where pcount < 0 caused errors
- removed duplicated code in mgr
- fix for problem with bvrecv() optimization
- more unused code removal
- adjustments to keep portland group compiler happy
- removed sd_path from metadata
- new iod.rc and mgr.rc files
- fixes to chmod
- fixes to get correct fs_ino back to clients
- multiple mtime fixes
- streamlined pvfs file detection
- shared library building
- fixed closing socket bug in iod
- reordered messaging in mgr to iods to improve concurrency
- rename fix
- improved metadata file checking
- do_access permission fixes
- fix for "iod out of space" client hang
- cleaner dead socket handling, including special handling of case where mgr would close fds that clients were using
- noninteractive mkmgrconf
<<lessThe PVFS project is conducted jointly between The Parallel Architecture Research Laboratory at Clemson University and The Mathematics and Computer Science Division at Argonne National Laboratory.
Additional funding for the PVFS project comes from NASA Goddard Space Flight Center Code 930 and The National Computational Science Alliance through the National Science Foundations Partnerships for Advanced Computational Infrastructure.
Main features:
- Compatibility with existing binaries
- Ease of installation
- User-controlled striping of files across nodes
- Multiple interfaces, including a MPI-IO interface via ROMIO
- Utilizes commodity network and storage hardware
PVFS supports the UNIX I/O interface and allows existing UNIX I/O programs to use PVFS files without recompiling. The familiar UNIX file tools (ls, cp, rm, etc.) will all operate on PVFS files and directories as well. This is accomplished via a Linux kernel module which is provided as a separate package.
PVFS is easy to install. The Quick Start page describes how to set up a simple installation. Scripts and test applications are included to help with configuration, testing for correct operation, and performance evaluation.
PVFS stripes file data across multiple disks in different nodes in a cluster. By spreading out file data in this manner, larger files can be created, potential bandwidth is increased, and network bottlenecks are minimized. A 64-bit interface is implemented as well, allowing large (more than 2GB) files to be created and accessed.
Enhancements:
- fixes to build under redhat 2.4.20-20.9 kernel
- checks for missing headers on ancient 2.4 kernels
- removal of unused fields from metadata and control messages
- updated pvfsd rc file
- handle various combinations of redhat kernel patches
- fixes to kpvfsd that had previously been fixed in user space
- fix for sftp directory reading problems
- fix to avoid oopses on clients when bad errno values returned
- adjustments to deal wiht gcc 3.4.0 issues
- fixes to work with redhat 9
- fixes to compile kernel code for xx86_64
- updated logging intrastructure
- fixes to error reporting
- update of makefile in pvfs core
- fix to bug in pvfs_open.c where pcount < 0 caused errors
- removed duplicated code in mgr
- fix for problem with bvrecv() optimization
- more unused code removal
- adjustments to keep portland group compiler happy
- removed sd_path from metadata
- new iod.rc and mgr.rc files
- fixes to chmod
- fixes to get correct fs_ino back to clients
- multiple mtime fixes
- streamlined pvfs file detection
- shared library building
- fixed closing socket bug in iod
- reordered messaging in mgr to iods to improve concurrency
- rename fix
- improved metadata file checking
- do_access permission fixes
- fix for "iod out of space" client hang
- cleaner dead socket handling, including special handling of case where mgr would close fds that clients were using
- noninteractive mkmgrconf
Download (0.23MB)
Added: 2005-04-08 License: GPL (GNU General Public License) Price:
1659 downloads
Eureka Encryption Global Edition 6.0
Eureka Encryption Global Edition contains file encryption, multiple encryption, merge encryption and more. more>>
Eureka Encryption Global Edition contains file encryption, multiple encryption, merge encryption, multiple file encryption, embedded applications (Crypt Words, Steganographer, Interface) and other tools such as a file shredder and scrambler.
Eureka Encryption Global Edition is available for Windows, Mac and Linux. Other applications are available from the website.
<<lessEureka Encryption Global Edition is available for Windows, Mac and Linux. Other applications are available from the website.
Download (5.5MB)
Added: 2007-05-09 License: Freeware Price:
899 downloads
sshutout 1.0.3
sshutout is a daemon that periodically monitors log files, looking for multiple failed login attempts via the Secure Shell daemo more>>
sshutout is a daemon that periodically monitors log files, looking for multiple failed login attempts via the Secure Shell daemon.
sshutout is meant to mitigate what are commonly known as "dictionary attacks," i.e. scripted brute force attacks that use lists of user IDs and passwords to effect unauthorized intrusions.
The sshutout daemon blunts such attacks by creating firewall rules to block individual offenders from accessing the system. These rules are created when an attack signature is detected, and after a configurable expiry interval has elapsed, the rules are deleted.
The sshutout algorithm follows a pretty standard model for *nix daemons. The program starts, assumes a fairly safe set of built-in default values, then consults an optional configuration file to further refine these values, and finally consults the command line for arguments specifying overrides. The program checks to see that it has the required superuser authority and then forks. Its newly forked daemon process detaches from the console; the original process terminates.
Next, an initial whitelist is constructed from the addresses of all active network interfaces. In addition, the name servers and default route are added to this whitelist. Finally, host addresses specified in the configuration file or command line are appended to the list.
Appropriate signal handling is now set up. In this case, SIGHUP, the hang-up signal, is provided with a handler to refresh the daemons operating parameters from the configuration file. The other handled signals, i.e. SIGTERM and SIGPWR (and possibly SIGINT and SIGQUIT if not running as a daemon), are set up to cause a graceful termination of the daemon process.
After signal handling has been initialized, the daemon enters its main processing loop. The loop spends most of its time in a sleep state, but when it does execute, which is approximately once per second, it examines all entries in its blocked hosts list to see if any are ready to expire. Those that are expiring are removed from the list and are also unblocked at the firewall through removal of the corresponding rule.
The daemons next action is to determine whether its polling interval has elapsed. If it has not yet elapsed, then the daemon goes back to sleep. If the interval has elapsed, then the daemon examines the hosts configuration to see if any changes are required to the whitelist, for example, if any new interfaces have come up, or if the addresses associated with any interfaces have changed, etc.
Next, the daemon will examine the specified log file to look for failed login attempts. It tallies a count of all failed login attempts for each unique host address over the span of the given polling interval. Those tallies that exceed the specified threshold are moved to the list of blocked hosts (unless, of course, they are in the whitelist.) Each item added to the blocked list is also blocked at the firewall through the addition of an suitable rule. This processing continues indefinitely until the daemon is signaled to stop.
Installation:
$ su -
# tar -xzvf sshutout-1.0.0.tar.gz
# cd sshutout-1.0.0
# make
# make install
Enhancements:
- This release adds the -u command line option to enable blocking of "Illegal user" login attempts.
- This option is also configurable via the configuration file.
<<lesssshutout is meant to mitigate what are commonly known as "dictionary attacks," i.e. scripted brute force attacks that use lists of user IDs and passwords to effect unauthorized intrusions.
The sshutout daemon blunts such attacks by creating firewall rules to block individual offenders from accessing the system. These rules are created when an attack signature is detected, and after a configurable expiry interval has elapsed, the rules are deleted.
The sshutout algorithm follows a pretty standard model for *nix daemons. The program starts, assumes a fairly safe set of built-in default values, then consults an optional configuration file to further refine these values, and finally consults the command line for arguments specifying overrides. The program checks to see that it has the required superuser authority and then forks. Its newly forked daemon process detaches from the console; the original process terminates.
Next, an initial whitelist is constructed from the addresses of all active network interfaces. In addition, the name servers and default route are added to this whitelist. Finally, host addresses specified in the configuration file or command line are appended to the list.
Appropriate signal handling is now set up. In this case, SIGHUP, the hang-up signal, is provided with a handler to refresh the daemons operating parameters from the configuration file. The other handled signals, i.e. SIGTERM and SIGPWR (and possibly SIGINT and SIGQUIT if not running as a daemon), are set up to cause a graceful termination of the daemon process.
After signal handling has been initialized, the daemon enters its main processing loop. The loop spends most of its time in a sleep state, but when it does execute, which is approximately once per second, it examines all entries in its blocked hosts list to see if any are ready to expire. Those that are expiring are removed from the list and are also unblocked at the firewall through removal of the corresponding rule.
The daemons next action is to determine whether its polling interval has elapsed. If it has not yet elapsed, then the daemon goes back to sleep. If the interval has elapsed, then the daemon examines the hosts configuration to see if any changes are required to the whitelist, for example, if any new interfaces have come up, or if the addresses associated with any interfaces have changed, etc.
Next, the daemon will examine the specified log file to look for failed login attempts. It tallies a count of all failed login attempts for each unique host address over the span of the given polling interval. Those tallies that exceed the specified threshold are moved to the list of blocked hosts (unless, of course, they are in the whitelist.) Each item added to the blocked list is also blocked at the firewall through the addition of an suitable rule. This processing continues indefinitely until the daemon is signaled to stop.
Installation:
$ su -
# tar -xzvf sshutout-1.0.0.tar.gz
# cd sshutout-1.0.0
# make
# make install
Enhancements:
- This release adds the -u command line option to enable blocking of "Illegal user" login attempts.
- This option is also configurable via the configuration file.
Download (0.030MB)
Added: 2006-06-30 License: GPL (GNU General Public License) Price:
1213 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above how to rename multiple files search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed