Free find 0.06 software for linux

jsFind is a Perl module that can generate index for full text search engine in JavaScript.

SYNOPSIS

use jsFind;
my $t = new jsFind(B => 4);
my $f = 1;
foreach my $k (qw{minima ut dolorem sapiente voluptatem}) {
$t->B_search(Key => $k,
Data => {
"path" => {
t => "word $k",
f => $f },
},
Insert => 1,
Append => 1,
);
}

This module can be used to create index files for jsFind, powerful tool for adding a search engine to a CDROM archive or catalog without requiring the user to install anything.

Main difference between this module and scripts delivered with jsFind are:
You dont need to use swish-e to create index

you can programatically (and incrementaly) create index for jsFind
you can create more than one index and search them using same search.html page

You can also examine examples which come as tests with this module, for example t/04words.t or t/10homer.t.

jsFind

jsFind search engine was written by Shawn Garbett from eLucid Software. The search engine itself is a small piece of JavaScript (1.2 with level 2 DOM). It is easily customizable to fit into a current set of HTML. This JavaScript searches an XML index dataset for the appropriate links, and can filter and sort the results.

JavaScript code distributed with this module is based on version 0.0.3 which was current when this module development started. Various changes where done on JavaScript code to fix bugs, add features and remove warnings. For complete list see Changes file which comes with distribution.

This module has been tested using html/test.html with following browsers:

Mozilla FireFox 0.8 to 1.0

using DOM 2 document.implementation.createDocument

Internet Explorer 5.5 and 6.0

using ActiveX Microsoft.XMLDOM or MSXML2.DOMDocument

Konqueror 3.3

using DOM 2 document.implementation.createDocument

Opera 7.54 (without Java)

using experimental iframe implementation which is much slower than other methods.

If searching doesnt work for your combination of operating system and browser, please open html/test.html file and wait a while. It will search sample file included with distribution and report results. Reports with included test debugging are welcomed.

pmping provides a parallel multiple host ping with audible results (beep on the PC speaker).
pmping is a script that pings multiple hosts in parallel and gives audible results depending on host state.
The sounds come from the internal PC speaker, thus not needing a sound card. It beeps when a host OS is losing many packets, or when it is down.
If the host is down, the script can send an email notification or run a command. All aspects are fully customisable by the user.
Main features:
- Logs notifications to standard output.
- Reloads config file on-the-fly.
- Ability to run a command when a host is down.
- Sends e-mail notifications when a host is down and when it comes up.
Enhancements:
- Corrected dynamic config reload (wasnt really working).
- Try to catch SMTP connection errors when sending notification e-mails.
- Changed the way we check network errors (regex was not working).

C is pronounced large-C and is a pseudo-interpreter of the C programming language.
Without the need of manual compilation, developers can rapidly create cross-platform scripts or write one-liners using the C/C++ programming language that run at native code speed.
Enhancements:
- The -S option was added to show disassembly.

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.

rfsdelta is a kernel module for the Linux 2.6 series that collects all filesystem inode changes (recursively) and reports them to a userspace process.
It is similar to inotify, dnotify (but provides recursive notification, and only a single watcher process is allowed), fschange, fsevent, and rlocate (but also reports unlink(), rmdir(), and st_*).
This project was based on the kernel module shipped with rlocate 0.5.5.
Version restrictions:
- Only one watch per system: the 2nd attempt to open rfsdelta-events will give `Device or resource busy.
- Doesnt work with rlocate.ko or any other security module (registered with register_security()). A subsequent call to register_security will yield `Invalid parameters. (This shouldnt be hard to fix provided that rlocate.ko is the first security module to be loaded.)
How to compile and install
You need a Linux 2.6 kernel source tree, and a kernel with these settings:
CONFIG_MODULES=y
CONFIG_SECURITY=y
CONFIG_SECURITY_CAPABILITES: disabled or module (=m)
In the folder containing `rfsdelta, run
$ make
This has built the rfsdelta.ko kernel module.
As root, run this to try:
# insmod rfsdelta.ko
# cat /proc/rfsdelta
# rmmod rfsdelta
As root, run these to install:
# make install
# modprobe rfsdelta
To try it, as root start
# tr 00 n
If you are not using udev or devfs, create the device manually:
# mknod /dev/rfsdelta-event `perl -pe$_ x=s@^devnumbers:@@ /proc/rfsdelta`
How to configure
If you want to force a specific character device major number (and minor number 0) for rfsdelta-event (instead of letting the kernel allocate one automatically), use
# modprobe rfsdelta major=< int >
You can change a couple of settings in /proc/rfsdelta. Run this command
as root:
# echo < key >:< value > >/proc/rfsdelta

File::AnySpec is a Perl module to perform operations on foreign (remote) file names.

SYNOPSIS

# Subroutine Interface
#
use File::AnySpec qw(fspec2fspec pm2fspec os2fspec fspec2os fspec_glob fspec2pm);

$file = fspec2fspec($from_fspec, $to_fspec $fspec_file, [$nofile])
$os_file = fspec2os($fspec, $file, [$no_file])
$fspec_file = os2fspec($fspec, $file, [$no_file])

$pm = fspec2pm($fspec, $require_file)
($abs_file, $inc_path, $require_file) = pm2fspec($fspec, $pm)

@globed_files = fspec_glob($fspec, @files)


# Class Interface
#
use File::AnySpec
use vars qw(@ISA)
@ISA = qw(File::AnySpec)

$file = __PACKAGE__->fspec2fspec($from_fspec, $to_fspec $fspec_file, [$nofile])
$os_file = __PACKAGE__->fspec2os($fspec, $file, [$no_file])
$fspec_file = __PACKAGE__->os2fspec($fspec, $file, [$no_file])

$pm = __PACKAGE__->fspec2pm($fspec, $require_file)
($abs_file, $inc_path, $require_file) = __PACKAGE__->pm2fspec($fspec, $pm)

@globed_files = __PACKAGE__->fspec_glob($fspec, @files)

Methods in this package, perform operations on file specifications for operating systems other then the current site operating system. The input variable $fspec tells the methods in this package the file specification for file names used as input to the methods. Thus, when using methods in this package, the method may load up to two File::Spec submodules methods and neither of them is a submodule for the current site operating system.

XML::IODEF is a Perl module for building/parsing IODEF messages.

QUICK START

Below is an example of an Incident IODEF message.
< ?xml version="1.0" encoding="UTF-8"?>
< !DOCTYPE IODEF-Message PUBLIC "-//IETF//DTD RFC XXXX IODEF v1.0//EN" "IODEF-Document.dtd">
< IODEF-Document>
< Incident purpose="handling">
< IncidentID>
#12345
< /IncidentID>
< AdditionalData meaning="data2" type="string">value2< /AdditionalData>
< AdditionalData meaning="data1" type="string">value1< /AdditionalData>
< /Incident>
< /IODEF-Document>
The previous IODEF message can be built with the following code snipset:
use XML::IODEF;

my $iodef = new XML::IODEF();

$iodef->add("Incidentpurpose", "handling");
$iodef->add("IncidentAdditionalData", "value1", "data1");
$iodef->add("IncidentAdditionalData", "value2", "data2");
$iodef->add("IncidentIncidentID", "#12345");

print $iodef->out();
To automatically insert an the ReportTime class to the current time, add the 2 lines:
$iodef->create_time();
and you will get (for example):
< ?xml version="1.0" encoding="UTF-8"?>
< !DOCTYPE IODEF-Message PUBLIC "-//IETF//DTD RFC XXXX IODEF v1.0//EN" "IODEF-Document.dtd">
< IODEF-Document>
< Incident purpose="handling">
< IncidentID>
#12345
< /IncidentID>
< IncidentData>
< ReportTime ntpstamp="0xc28859cf.0x0">2003-06-04-T11:43:11Z">2003-06-04-T11:43:11Z< /ReportTime>
< AdditionalData meaning="data2" type="string">value2
< AdditionalData meaning="data1" type="string">value1
< /Incident>
< /IODEF-Document>

MP3::Find::Filesystem is a File::Find-based backend to MP3::Find.

SYNOPSIS

use MP3::Find::Filesystem;
my $finder = MP3::Find::Filesystem->new;

my @mp3s = $finder->find_mp3s(
dir => /home/peter/music,
query => {
artist => ilyaimy,
album => myxomatosis,
},
ignore_case => 1,
);