Free how do i find a person software for linux

File::Find::Similars is a Similar files locator.

SYNOPSIS

use File::Find::Similars;

File::Find::Similars->init(0, @ARGV);
similarity_check_name();

Similar-sized and similar-named files are picked as suspicious candidates of duplicated files.

What descirbes it better than a actual output. Sample suspicious duplicated files:

## =========
1574 PopupTest.java /home/tong/.../examples/chap10
1561 CardLayoutTest.java /home/tong/.../examples/chap1
1570 PopupButtonFrame.class /home/tong/.../examples/chap6

## =========
22984 BinderyHelloWorld.jpg /home/tong/...
17509 MacHelloWorld.gif /home/tong/...

The first column is the size of the file, 2nd the name, and 3rd the path. The motto for the listing is that, I would rather my program overkills (wrongly picking out suspicious ones) than neglects something that would cause me otherwise years to notice.
By default, File::Find::Similars(3) assumes that similar files within the same folder are OK. Hence you will not get duplicate warnings for generated files (like .o, .class or .aux, and .dvi files) or other file series.

Once you are sure that there are no duplications between folders and want File::Find::Similars(3) to scoop further, specify the first parameter as 1. This is very good to eliminate similar mp3 files within the same folder, or downloaded files from big sites where different packaging methods are used, e.g.:

## =========
66138 jdc-src.tar.gz .../ftp.ora.com/published/oreilly/java/javadc
147904 jdc-src.zip .../ftp.ora.com/published/oreilly/java/javadc

NetAddr::IP::Find is a Perl module to find IP addresses in plain text.

SYNOPSIS

use NetAddr::IP::Find;
$num_found = find_ipaddrs($text, &callback);

This is a module for finding IP addresses in plain text.

Functions

NetAddr::IP::Find exports one function, find_ipaddrs(). It works very similar to URI::Finds find_uris() or Email::Finds find_emails().

$num_ipaddrs_found = find_ipaddrs($text, &callback);

The first argument is a text to search through and manipulate. Second is a callback routine which defines what to do with each IP address as theyre found. It returns the total number of IP addresses found.

The callback is given two arguments. The first is a NetAddr::IP instance representing the IP address found. The second is the actual IP address as found in the text. Whatever the callback returns will replace the original text.

EXAMPLES

# For each IP address found, ping its host to see if its alive.
use Net::Ping;
my $pinger = Net::Ping->new;
my %pinged;
find_ipaddrs($text, sub {
my($ipaddr, $orig) = @_;
my $host = $ipaddr->to_string;
next if exists $pinged{$host};
$pinged{$host} = $pinger->ping($host);
});

while (my($host, $up) == each %pinged) {
print "$host is " . $up ? up : down . "n";
}


# Resolve IP address to FQDN
find_ipaddrs($text, sub {
my($ipaddr, $orig) = @_;
resolve_ip($ipaddr->to_string);
});

sub resolve_ip {
use Net::DNS;
# see perldoc Net::DNS for details
}

Email::Find allows you to find RFC 822 email addresses in plain text.

Email::Find is a module for finding a subset of RFC 822 email addresses in arbitrary text (see "CAVEATS"). The addresses it finds are not guaranteed to exist or even actually be email addresses at all (see "CAVEATS"), but they will be valid RFC 822 syntax.

Email::Find will perform some heuristics to avoid some of the more obvious red herrings and false addresses, but theres only so much which can be done without a human.

Finds email addresses in the text and executes callback registered.

The callback is given two arguments. The first is a Mail::Address object representing the address found. The second is the actual original email as found in the text. Whatever the callback returns will replace the original text.

File::Find::Parallel allows you to traverse a number of similar directories in parallel.

SYNOPSIS

use File::Find::Parallel;

my $ffp = File::Find::Parallel->new( qw( /foo /bar ) );

print "Union:n";
my $union = $ffp->any_iterator
print " $_n" while $_ = $union->();

print "Intersection:n";
my $inter = $ffp->all_iterator
print " $_n" while $_ = $inter->();

File::Find is the ideal tool for quickly scanning a single directory. But sometimes its nice to be able to perform operations on multiple similar directories in parallel. Perhaps you need to compare the contents of two directories or convert files that are shared in more than one directory into hard links.

This module manufactures iterators that visit each file and directory in either the union or the intersection of a number of directories. Hmm. What does that mean?

Given two directory trees like this

foo
foo/a
foo/b/c
foo/d

bar
bar/a
bar/b
bar/e

you can choose to work with the intersection of the two directory structures:
.
./a
./b

That is the subdirectories and files that the foo and bar share.
Alternately you can work with the union of the two directory structures:
.
./a
./b
./b/c
./d
./e

Still not clear? Well, if you wanted to do a recursive diff on the two directories youd iterate their union so you could report files that were present in foo but missing from bar and vice-versa.

If, on the other hand you wanted to scan the directories and find all the files that are common to all of them youd iterate their intersection and receive only files and directories that were present in all the directories being scanned.

The any_iterator and all_iterator are built on a more general purpose method: want_iterator. If, for example, you want to make links between files that are found in more than one directory you might get your iterator like this:

my $iter = $ffp->want_iterator( 2 );

The apparently magic 2 reflects the fact that if youre going to be making links you need at least two files. No matter how many directories you are iterating over in parallel you will only see files and directories that appear in at least two of those directories.

File::Find::Parallel can scan any number of directories at the same time. Heres an example (on Unix systems) that returns the list of all files and directories that are contained in all home directories.

use File::Glob :glob;
use File::Find::Parallel;

my $find = File::Find::Parallel->new( bsd_glob( /home/* ) );

my @common = ( );
my $iter = $find->all_iterator;
while ( defined my $obj = $iter->() ) {
push @common, $obj;
}

print "The following files are common to ",
"all directories below /home :n";

print " $_n" for @common;

For a complete concrete example of its use see lncopies in the bin subdirectory of this distribution.

Iterators

The iterator returned by any_iterator, all_iterator or want_iterator is a code reference. Call it to get the next file or directory. When all files and directories have been returned the iterator will return undef.

Once created an iterator is independent of the File::Find::Parallel object that created it. If the object goes out of scope and is destroyed during the life of the iterator it will still function normally.

You may have many active iterators for a single File::Find::Parallel object at any time.

KoffeePhoto is a free software that allows you to manage your personal photo library. You can manage your photo albums with KoffeePhoto, and share them with your friends or family very easily. Your albums will be saved on the KoffeePhoto network, which will let you access them anytime and anywhere.

KoffeePhoto allows you to pick your photos on your hard disk or on your camera, and to organize them in albums. Thanks to several ways of sorting your photos, by date, topic, place, person, or any combination of these categories, you will always have an easy way to find all your photos again.

KoffeePhoto saves your whole photo library on its peer-to-peer KoffeePhoto network. This is carried out in a completely seamless way. Your photos are encrypted to ensure confidentiality, and are saved without any loss in quality (no format reduction, no data compression), and no storage expiration date. You can access your photo library from several computers if you wish. In case of any data loss, you can recover your whole photo library very easily!

SYNOPSIS

use File::Find::Rule;
# find all the subdirectories of a given directory
my @subdirs = File::Find::Rule->directory->in( $directory );

# find all the .pm files in @INC
my @files = File::Find::Rule->file()
->name( *.pm )
->in( @INC );

# as above, but without method chaining
my $rule = File::Find::Rule->new;
$rule->file;
$rule->name( *.pm );
my @files = $rule->in( @INC );

MP3::Find is a Perl module to search and sort MP3 files based on their ID3 tags.

SYNOPSIS

# select with backend you want
use MP3::Find qw(Filesystem);

print "$_n" foreach find_mp3s(
dir => /home/peter/cds,
query => {
artist => ilyaimy,
title => deep in the am,
},
ignore_case => 1,
exact_match => 1,
sort => [qw(year album tracknum)],
printf => %2n. %a - %t (%b: %y),
);

This module allows you to search for MP3 files by their ID3 tags. You can ask for the results to be sorted by one or more of those tags, and return either the list of filenames (the deault), a printf-style formatted string for each file using its ID3 tags, or the actual Perl data structure representing the results.

There are currently two backends to this module: MP3::Find::Filesystem and MP3::Find::DB. You choose which one you want by passing its name as the argument to you use statement; MP3::Find will look for a MP3::Find::$BACKEND module. If no backend name is given, it will default to using MP3::Find::Filesystem.
Note: Im still working out some kinks in the DB backend, so it is currently not as stable as the Filesystem backend.

Note the second: This whole project is still in the alpha stage, so I can make no guarentees that there wont be significant interface changes in the next few versions or so. Also, comments about what about the API rocks (or sucks!) are appreciated.

KPhotoAlbum program (formerly known as KimDaBa, KDE Image Database) is a tool for indexing, searching, and viewing images. The indexing is done by telling KPhotoAlbum who is on the images, where the images were taken, and (optionally) adding descriptions.
It is highly optimized for easy indexing of images, so that it is possible to use it with thousands of images. It also allows you to browse your images easily, based on the properties (person, location, keywords) you specified when indexing.
I personally realized that this was not possible anymore, and especially for my digital images - but also for my paper images - I needed a tool to help me describe my images, and to search in the pile of images. This is exactly what KPhotoAlbum is all about.
With KPhotoAlbum it is today possible for me to find any image I have in less than 5 seconds, let that be an image with a special person, an image from a special place, or even both.
There is of course no such thing as free lunch - with KPhotoAlbum this means that you have to annotate all your images before you are set. KPhotoAlbum is, however, highly optimized for annotating images, so annotating 100 images in 10 minutes are no way impossible.
Enhancements:
- Video Support
- Much improved subcategory support.