Free zoned software for linux

Zoned project provides DNS zone database clustering for BIND9.

Zoned works in conjunction with the BDBHPT DLZ module for BIND9 (9.4.0+). Zoned manages the backing-store Berkeley DB database, and utilizes the Berkeley DB Replication Base API to provide high availability and load distribution to a coherent DNS zone infrastructure.

Zoned includes the zoned(1) server replication node, zonectl(1) command line utility for managing server nodes and editing DNS zone records, and a Perl module, Zoned. All changes to DNS zone data must be processed through a Zoned node, preferably using the command-line utility or Perl library. Alternatively, an ASN.1 message schema definition is provided, defining the messaging protocol for node communication, which can be used to build your own tools for interacting with the cluster.

Zoned and Berkeley DB autonomously manage the cluster and cluster messaging (including transparently routing all zoned edits to the master, per BerkeleyDB Replication requirements). You must enumerate cluster nodes through SRV resource records. This list specifies all nodes which should participate in the cluster, not necessarily all available nodes. This list determines who and where each node should peer with, and serves as a parameter to determining whether a transaction has been successfully committed (more than one-half of enumerated nodes have written out a zone edit). The SRV node enumeration modifications are automatically detected with a configurable check interval.

To compile Zoned you need: GNU Make, libarena, libevnet, libevent, asn1c, and Lua.

Zoned has been successfully compiled and run on Debian GNU/Linux i386, and OpenBSD 4.0 AMD64 platforms. Zoned is new software, and it may take some elbow grease to build properly.

libevnet requires C-Ares and OpenSSL.

Zoned is a Work-in-Progress. Node authentication is not yet implemented, but will use TLS and X.509 certificate verification. Currently node discovery occurs through an SRV query, which is expected to enumerate all current nodes.

ZoneMinder is a suite of applications intended for use in video camera security applications, including theft prevention and child or family member monitoring. The project supports capture, analysis, recording, and monitoring of video data coming from one or more video or network cameras attached to a Linux system.

It also features a user-friendly Web interface which allows viewing, archival, review, and deletion of images and movies captured by the cameras. The image analysis system is highly configurable, permitting retention of specific events, while eliminating false positives.

ZoneMinder supports both directly connected and network cameras and is built around the definition of a set of individual zones of varying sensitivity and functionality for each camera. This allows the elimination of regions which should be ignored or the definition of areas which will alarm if various thresholds are exceeded in conjunction with other zones. All management, control, and other functions are supported through the Web interface.

DNS::Zone contains a collection of Perl modules which provide an abstraction of name service zones as well as server specific adaptors for concrete file representations.

The modules origin is the ZoneMaster project which make heavy use of the module for comprehensive zone file management. Go to http://www.zonemaster.org for further information.

Installation:

You install DNS::Zone as you would install any perl module library, by running these command:

If you have CPAN.pm installed and are connected to the Internet

perl -MCPAN -e shell
> install DNS::Zone

or even

perl -MCPAN -e install DNS::Zone

otherwise

perl Makefile.PL
make
make test
make install

Time::Zone is a miscellaneous timezone manipulations routines.

SYNOPSIS

use Time::Zone;
print tz2zone();
print tz2zone($ENV{TZ});
print tz2zone($ENV{TZ}, time());
print tz2zone($ENV{TZ}, undef, $isdst);
$offset = tz_local_offset();
$offset = tz_offset($TZ);

This is a collection of miscellaneous timezone manipulation routines.
tz2zone() parses the TZ environment variable and returns a timezone string suitable for inclusion in date-like output. It opionally takes a timezone string, a time, and a is-dst flag.

tz_local_offset() determins the offset from GMT time in seconds. It only does the calculation once.

tz_offset() determines the offset from GMT in seconds of a specified timezone.
tz_name() determines the name of the timezone based on its offset

DIY Zoning is a repository containing the information about architecting, designing and implementing the Do It Yourself Temperature Zoning system, introductory course for those planning to install a ready-made temperature zoning system, and those who just want their home comfort.

Whats New in This Release:

This release introduces support for many logical devices per one physical 1-Wire device in general, and humidity sensor support in particular.

DAC2CORE protocol has changed, backward compatibility is broken. To upgrade your configuration, you have to add a literal T in front of 1-Wire temperature sensors, and add a literal S in front of 1-Wire switch devices.

SYNOPSIS

use Math::FresnelZone;
use Math::FresnelZone qw(fresnel fresnelMi fresnelKm);

The arguments are:

0 - distance in kilometers or miles (default is 1),
1 - frequency in GHz (defualt 2.4),
2 - set to true to specify that the distance you are inputting is in miles and that the results should be in in feet (default is 0 - IE kilometers/meters)
fresnel()

my $fresnel_zone_radius_in_meters = fresnel(); # fresnel zone radius in meters for 1 kilometer at 2.4 GHz

my $fzr_in_meters = fresnel(5); # fresnel zone radius in meters for 5 kilometers at 2.4 GHz

my $fzr_in_meters = fresnel(5,4.8); # fresnel zone radius in meters for 5 kilometers at 4.8 GHz

my $fzr_in_feet = fresnel(3,9.6,1); # fresnel zone in feet for 3 miles at 9.6 GHz

If you are inputting Kilometers the result is in meters (these 3 calls have identical results):

fresnel($Km,$GHz);
fresnelKm($Km,$GHz); # see documentaion below for info about fresnelKm()
fresnel($Km,$GHz,0);

If you are inputting Miles (by specifying a true value as the 3rd argument) the result is in feet (these 2 calls have identical results)

fresnel($Mi,$GHz,1);
fresnelMi($Mi,$GHz); # see documentaion below for info about fresnelMi()

fresnelKm()

You can use this to make it easier to avoid ambiguity if are working in kilometers/meters. It takes the first two arguments only: distance in kilometers and frequency in GigaHertz

my $fzr_in_meters = fresnelKm($Km,$GHz);

fresnelMi()

You can use this to make it easier to avoid ambiguity if are working in miles/feet. It takes the first two arguments only: distance in miles and frequency in GigaHertz

my $fzr_in_feet = fresnelMi($Mi,$GHz);

NSD is a complete implementation of an authoritative DNS nameserver.
NSD is an authoritative only, high performance, simple and open source name server.
NSD is thoroughly tested, there is a regression tests report available on the home page.
NLnet Labs has a long term commitment for supporting NSD. There will be an advanced notice when our commitment ends. The latest NSD release will supported for at least two years after this notice.
Enhancements:
- AXFR/IXFR zone transfer supported.
- NSD requests but does not provide IXFR transfers.
- NSD keeps track of SOA timeouts for secondary zones.
- TSIG authentication supported.
- For queries, for notifies, for zone transfers.
- NOTIFY messages of zone updates, incoming and outgoing.
- DNAME type is supported, including CNAME synthesis.
- config file, nsd.conf(5), place to put TSIG keys, server settings, and lists of ip-addresses/ranges for AXFR/IXFR and NOTIFY.

Rose::DateTime is a Perl module with DateTime helper functions and objects.

SYNOPSIS

use Rose::DateTime::Util qw(:all);

$now = parse_date(now);
$then = parse_date(12/25/2001 6pm);

$date_text = format_date($then, "%D at %T %p");

...

use Rose::DateTime::Parser;

$parser = Rose::DateTime::Parser->new(time_zone => UTC);

$date = $parser->parse_date(12/25/1999);

The Rose::DateTime::* modules provide a few convenience functions and objects for use with DateTime dates.

Rose::DateTime::Util contains a simple date parser and a slightly customized date formatter.

Rose::DateTime::Parser encapsulates a date parser with an associated default time zone.

This module (Rose::DateTime) exists mostly to provide a version number for CPAN. See the individual modules for some actual documentation.