Free could not reliably determine the serveru0027s fully qualified domain name software for linux

OpenInteract::UI::Main is the primary user interface assembly conductor.

SYNOPSIS

my $page = OpenInteract::UI::Main->handler();
send_http_headers();
print $page;

# Subclass to define a new method for looking up template names:

package OpenInteract::UI::LanguageChoice;

use base qw( OpenInteract::UI::Main );

my $DEFAULT_LANGUAGE = en;

sub choose_template {
my ( $class ) = @_;
my ( $language );
if ( $R->{auth}{is_logged_in} ) {
$language = $R->{auth}{user}->language;
}
$language ||= $R->apache->param( lang )
|| $R->{session}{lang}
|| $DEFAULT_LANGUAGE;
my $R = OpenInteract::Request->instance;
my $template = $R->{theme}->property_value( "template_$language" )
|| $R->{theme}->property_value( main_template );
return $template;
}

This is the handler that puts the main content generated together with the template that surrounds the content on every page.

The action has already been parsed from the URL for us so we look up the class/method used to generate the content and call them. We then put that content into the main template which is specified in our theme, unless we have received another directive to use a separate template or no template at all.

Another alternative is that the content handler needs to return a file that is not HTML, such as a PDF, graphic, word processing document, archive, or whatever. If so the content handler should put the complete filename in the $R->{page}->{send_file} key.

A content author can set a main template to use for the generated content by setting:

$R->{page}{_template_name_}

to the name of the template to use. This should be a fully-qualified template name -- such as mypkg::mytemplate. If you do not specify a package the OI template provider will try to find the template in the global template directory.

You can also set a template that might vary by theme. This is not the name of the template directly but rather a placeholder within the theme which holds the name of the template. For instance, say you created a spooky_template and implemented it in multiple themes. Even though you as an author do not know what theme will be used, you can still pick the right template by setting:

$R->{page}{_template_key_}

And to use the simple template, the author should set:

$R->{page}{_simple_}

to a true value. The default simple template is base_simple, although you can set its name under the template_names key of your server configuration.

Finally, the author can also set:

$R->{page}{_no_template_}

to display the content without a template at all.

Main Template Variables

Any content handler can send information to be placed directly onto the main template by setting information using the $R->{main_template_vars} hashref. For instance:

$R->{main_template_vars}{current_weather} = Rainy and cold;

would set the current_weather template variable for display on the main template and not on any of the content handlers.

Note that while this sounds useful (and it can be), you will probably use it only very rarely. The boxes concept is more comprehensive and full-featured and will almost certainly do what you need.

Locale::TextDomain is a Perl Interface to Uniforum Message Translation.

SYNOPSIS

use Locale::TextDomain (my-package, @locale_dirs);

use Locale::TextDomain qw (my-package);

my $translated = __"Hello World!n";

my $alt = $__{"Hello World!n"};

my $alt2 = $__->{"Hello World!n"};

my @list = (N__"Hello", N__"World");

my @plurals = (N__ ("One world", "{num} worlds"),
N__ ("1 file", "%d files"));

my $question = __x ("Error reading file {file}: {err}",
file => $file, err => $!);

printf (__n ("one file read",
"%d files read",
$num_files),
$num_files);

print __nx ("one file read", "{num} files read", $num_files,
num => $num_files);

The module Locale::TextDomain(3pm) provides a high-level interface to Perl message translation.

Textdomains

When your request a translation for a given string, the system used in libintl-perl follows a standard strategy to find a suitable message catalog containing the translation: Unless you explicitely define a name for the message catalog, libintl-perl will assume that your catalog is called messages (unless you have changed the default value to something else via Locale::Messages(3pm), method textdomain()).
You might think that his default strategy leaves room for optimization and you are right. It would be a lot smarter if multiple software packages, all with their individual message catalogs, could be installed on one system, and it should also be possible that third-party components of your software (like Perl modules) can load their message catalogs, too, without interfering with yours.

The solution is clear, you have to assign a unique name to your message database, and you have to specify that name at run-time. That unique name is the so-called textdomain of your software package. The name is actually arbitrary but you should follow these best-practice guidelines to ensure maximum interoperability:

File System Safety

In practice, textdomains get mapped into file names, and you should therefore make sure that the textdomain you choose is a valid filename on every system that will run your software.

Case-sensitivity

Textdomains are always case-sensitive (i. e. Package and PACKAGE are not the same). However, since the message catalogs will be stored on file systems, that may or may not distinguish case when looking up file names, you should avoid potential conflicts here.

Textdomain Should Match CPAN Name

If your software is listed as a module on CPAN, you should simply choose the name on CPANS as your textdomain. The textdomain for libintl-perl is hence libintl-perl. But please replace all periods (.) in your package name with an underscore because ...

Internet Domain Names as a Fallback

... if your software is not a module listed on CPAN, as a last resort you should use the Java(tm) package scheme, i. e. choose an internet domain that you are owner of (or ask the owner of an internet domain) and concatenate your preferred textdomain with the reversed internet domain. Example: Your company runs the web-site www.foobar.org and is the owner of the domain foobar.org. The textdomain for your companys software barfoos should hence be org.foobar.barfoos.

If your software is likely to be installed in different versions on the same system, it is probably a good idea to append some version information to your textdomain.
Other systems are less strict with the naming scheme for textdomains but the phenomena known as Perl is actually a plethora of small, specialized modules and it is probably wisest to postulate some namespace model in order to avoid chaos.

Binding textdomains to directories

Once the system knows the textdomain of the message that you want to get translated into the users language, it still has to find the correct message catalog. By default, libintl-perl will look up the string in the translation database found in the directories /usr/share/locale and /usr/local/share/locale (in that order).

It is neither guaranteed that these directories exist on the target machine, nor can you be sure that the installation routine has write access to these locations. You can therefore instruct libintl-perl to search other directories prior to the default directories. Specifying a differnt search directory is called binding a textdomain to a directory.

Locale::TextDomain extends the default strategy by a Perl specific approach. Unless told otherwise, it will look for a directory LocaleData in every component found in the standard include path @INC and check for a database containing the message for your textdomain there. Example: If the path /usr/lib/perl/5.8.0/site_perl is in your @INC, you can install your translation files in /usr/lib/perl/5.8.0/site_perl/LocaleData, and they will be found at run-time.

Network Query Tool is a one-stop solution for obtaining information about a domain name or an IP address.
Instead of manually using a variety of shell commands, or visiting numerous websites to investigate a host, just load Network Query Tool in your browser and enter the hostname or IP. NQT does the rest, as is evidenced by this sample output.
Main features:
- Reverse lookup - resolves an IP address to a hostname (if one exists) or vice versa
- DNS query - aka Dig, requires a dig binary on your system
- Whois (WWW) - gets domain registration information. Now supporting just about every known TLD, gTLD, and ccTLD.
- Whois (IP) - gets IP owner information. Supports all IP blocks maintained by ARIN (US), RIPE (Europe), JPNIC (Japan), APNIC (China/Asia-Pacific), BRNIC (Brazil), LACNIC (Latin America), AFRINIC (Africa), and KRNIC (Korea).
- Check port - Determine whether or not a port on the target host is open. Defaults to port 80.
- Ping - performs a 5-packet ping to the target, requires a ping binary.
- Traceroute - performs a traceroute to the target, requires a traceroute binary.

Domain Name Portfolio is a PHP and MySQL based application to help domain owners better organize their portfolio.
It allows you to list your domains with their expiry, registrar, and a price.
Also allows visitors to your portfolio to contact you about a given domain.
Main features:
- Script features
Enhancements:
- This release brings support for MySQLi, along with minor bugfixes and several function improvements.

Log::Log4perl::Layout::PatternLayout Perl module contains a pattern layout.

SYNOPSIS

use Log::Log4perl::Layout::PatternLayout;

my $layout = Log::Log4perl::Layout::PatternLayout->new(
"%d (%F:%L)> %m");

Creates a pattern layout according to http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/PatternLayout.html and a couple of Log::Log4perl-specific extensions.

The new() method creates a new PatternLayout, specifying its log format. The format string can contain a number of placeholders which will be replaced by the logging engine when its time to log the message:

%c Category of the logging event.
%C Fully qualified package (or class) name of the caller
%d Current date in yyyy/MM/dd hh:mm:ss format
%F File where the logging event occurred
%H Hostname (if Sys::Hostname is available)
%l Fully qualified name of the calling method followed by the
callers source the file name and line number between
parentheses.
%L Line number within the file where the log statement was issued
%m The message to be logged
%M Method or function where the logging request was issued
%n Newline (OS-independent)
%p Priority of the logging event
%P pid of the current process
%r Number of milliseconds elapsed from program start to logging
event
%T A stack trace of functions called
%x The topmost NDC (see below)
%X{key} The entry key of the MDC (see below)
%% A literal percent (%) sign

NDC and MDC are explained in "Nested Diagnostic Context (NDC)" in Log::Log4perl and "Mapped Diagnostic Context (MDC)" in Log::Log4perl.
The granularity of time values is milliseconds if Time::HiRes is available. If not, only full seconds are used.

EtherEye is a web-based network host checking system written in PHP and standards compliant HTML.
You simply provide it with a list of IP addresses or domain names via the configuration interface and it will ping them on request and output the results as HTML.
You can also access the results via RSS feed for easier monitoring or to integrate into a website.
Installation:
To configure EtherEye, simply point your browser at the config.php file included with EtherEye. If it doesnt work or you get an error, PHP probably isnt properly configured on your server.
Language
Select your desired language here. This setting affects the language of the configuration interface as well as the results interface. Please read the README for instructions on how to translate EtherEye into your language if your language is not available.
Does the server run Windows?
If the server runs Windows, select "Yes", otherwise leave it on "No". If you set this to Yes, a few options will be filled in automatically, so you dont need to worry about them.
Which theme would you like to use?
Pretty self-explanatory really. The EtherEye interface will look different depending on which theme you select. Please see the README for instructions on how to write EtherEye themes.
Automatic refresh
If you enable automatic refreshing, the results page will be automatically re-loaded as frequently as specified by the option further down the page.
Ping command line option to specify the number of requests to send
If you selected the Windows server option you dont need to worry about this - it has been auto-filled. If not, the default should be OK for people running Linux. People running other UNIXes will need to check their ping man page.
Ping command line option to specify the ping timeout
The default value should be OK for everyone running Windows or Linux. Again, people running other UNIXes will need to check their ping man page.
Ping time-out
This value tells ping how long to wait for a response to ping requests. This value is in seconds if your server runs Linux or UNIX and milliseconds if your server runs Windows. The default value used by ping under Linux and UNIX is 3 seconds, Windows ping is 4000 milliseconds (4 seconds).
The lower this value, the less time EtherEye has to wait for ping to give up waiting for a response from a down machine, which makes the results get displayed quicker. However, bear in mind that if a machine is up but takes longer to respond than the time allowed by this value, EtherEye will report it as down! One second is probably a reasonable value for this setting.
Site name
This is simply a name used in a few places in the interface. It can be anything you want.
How often to refresh
If you enabled automatic refreshing above, you need to set this to how often you would like the results page to be automatically refreshed in seconds. The default, 300 seconds, is 5 minutes. If you didnt enable automatic refreshing above, you dont need to worry about this option.
How long to cache results for?
Each time EtherEye pings the hosts it saves the state of each host in the hosts file. This option determines how long these saved states are used for before EtherEye re-pings the hosts. If EtherEye has cached results available which have not expired, it will display them immediately without re-checking the hosts. This can be useful if you access EtherEye a lot (many times a minute) and dont need EtherEye to check the hosts that frequently. Most people will probably want to set this to 0 to disable caching completely.
Number of machines you want to watch
You need to specify here how many machines you want EtherEye to monitor. This is used to decide how many input boxes to give you on the next page.
If all is well, click on the button to save the options youve entered and move to the next page of the installation. If EtherEye is giving an error and not displaying the button, you need to check the permissions on the directory EtherEye is running from - you need to enable write access for all users (you can change it back later).
Entering the hosts
On this page, you need to enter the hosts you wish to monitor. Enter the IP address or domain name in the first box of each line, then a name for the machine in the second box (this can be anything you want) and finally select the machine type - this wont affect how EtherEye works, it is simply used to select an icon to display for the machine in the results.
Finishing the configuration
Once you have completed the installation, you may wish to change the permissions on the directory EtherEye is installed into so that every user cannot write to it (you cant be too careful).
Next, you may wish to change the permissions on the hosts-list.xml and ethereye-conf.xml files to ensure they are not writable (you dont want other people playing with your configuration). However, note that if you make hosts-list.xml non-writable, caching will not work (if you enabled it) and no error will be given to tell you this.
You may also wish to delete config.php for proper security, but then you wont be able to reconfigure EtherEye using the interface later.
Using EtherEye
Once you have EtherEye configured, you can check the machines you have configured EtherEye with by accessing the index.php file. If you use an RSS aggregator, you may wish to add rss.php to it to keep track of your network status. You could also integrate your EtherEye scan results into your website using the rss.php feed.
Enhancements:
- This release incorporates fixes for users receiving outdated results due to caching in the browser or server and for some configuration values not being remembered when reconfiguring using the configuration interface.