Free warning error writing vtoc software for linux

Unicode Error Detector is a product for Plone used to pinpoint errors in your application leading to UnicodeDecodeErrors.

Do not use this product unless you are actively debugging a Unicode Error. Never use this product in production sites.

UnicodeDecodeErrors typically occur when you try to add a Unicode string to a non-ascii string. This product patches StringIO used by page templates to check if the appended string is a Unicode string, and if it is, it replaces the string with an error marker.

As there is some overhead associated with inspecting the strings instead of just appending to the output, this product is meant for debugging purposes only.

Usage

Put the product in your Products directory and restart Zope. Load the template causing the UnicodeDecodeError, and this tool will indicate the location by printing THIS IS WHERE THE ERROR IS in the rendered template.

You can then inspect the template and/or code more closely to figure out where the decode error happens.

Syslog is a almost standard UN*X daemon which gathers all the info, errors or critical messages from the local computer or other hosts on the network. For more info about syslog itself, see the corresponding syslog manpages.
Before using Interceptor, you must create 8 fifo files in /var/run/interceptor, (debug, info, notice, warning, err, crit, alert, emerg) and modify the /etc/syslog.conf so that syslog sends its messages in the corresponding fifo for a given level, e.g.
*.debug |/var/run/interceptor/debug
The mkintfifos included script will update /etc/rc.d/rc.sysinit and /etc/syslog.conf for you. When done, restart your computer, install the interceptor applet and load it on the taskbar.
A button appears, which will flash green when a debug, info or notice message occurs, orange when a warning or error message occurs and red when crit, alert or emerg.
If you click on this button, a list of received messages will be displayed.
Interceptor can react to some messages according to a pattern->action scheme with up to 2 argument strings. The available actions are the following ones:
- Beep: Simply issues a beep.
- Message: Displays a dialog box with first arg string as the wanted message and optionnaly executes a shell command when the yes button is clicked. The command itself is contained in the second arg string.
- Redirect: Redirects the current message towards a specific log view.
- Run: Silently runs a shell command contained in arg string 2 and appends arg string 1 at the end of the system messages list.
Remark: if the first argument of a Run alert is null, the first line of the shell command stdout is appended to the messages list, with Info as the level and Interceptor as the source.
The pattern rules obey to the QRegExp syntax. See QRegExp in the Qt documentation for more details. In addition to the standard QRegExp syntax, Interceptor uses pattern groups, i.e. it can retrieve substring enclosed in group parenthesis. Example:
abc(.+)def
This group contains any string enclosed within abc and def. A substitution is made whenever a message matches with a given regexp. The variables $1, $2, $3 and $4 will be replaced with the corresponding pattern group in both arg 1 and arg 2 strings.
the variables $D and $T will be substituted with the current date and time
The patterns are tried against the
level##source!!host%%text
string, where level is debug, info etc..., source is the info source, i.e. kernel, the daemon name, lpr etc..., host is the hostname and text, the text of the message.
You can also choose a better suited icon, such as floppy, network or CDROM icons, for your dialog boxes.
When you select the preferences kicker applet menu, a tab widget will appears, which will allow you to edit the pattern->action rules, and some default options, such as the level colors and number of lines on the messages list box.
Enhancements:
- Aspects Scan list.
- A few bugs fixed.

Mac::Errors is a Perl module with constants for Mac error codes.

SYNOPSIS

use Mac::Errors qw(openErr);

if( $value == openErr ) { ... }

my $error = $MacErrors{ $symbol }; # -- OR -- my $error = $MacErrors{ $number };

my $symbol = $error->symbol; my $number = $error->number; my $desc = $error->description;

# in MacPerl, $^E is meaningful, and we tie $MacError to it use Mac::Errors qw( $MacError );

open FILE, $foo or die $^E; # error number open FILE, $foo or die $MacError; # gets description from $^E

The %MacErrors hash indexes error information by the error number or symbol. Each value is a Mac::Errors object which has the symbol, number, and description.

The $MacError scalar performs some tied magic to translate MacPerls $^E to the error text.

Net::DBus::Error is a Perl module with error details for remote method invocation.

SYNOPSIS

package Music::Player::UnknownFormat;

use base qw(Net::DBus::Error);

# Define an error type for unknown track encoding type
# for a music player service
sub new {
my $proto = shift;
my $class = ref($proto) || $proto;
my $self = $class->SUPER::new(name => "org.example.music.UnknownFormat",
message => "Unknown track encoding format");
}


package Music::Player::Engine;

...snip...

# Play either mp3 or ogg music tracks, otherwise
# thrown an error
sub play {
my $self = shift;
my $url = shift;

if ($url =~ /.(mp3|ogg)$/) {
...play the track
} else {
die Music::Player::UnknownFormat->new();
}
}

This objects provides for strongly typed error handling. Normally a service would simply call

die "some message text"

When returning the error condition to the calling DBus client, the message is associated with a generic error code or "org.freedesktop.DBus.Failed". While this suffices for many applications, occasionally it is desirable to be able to catch and handle specific error conditions. For such scenarios the service should create subclasses of the Net::DBus::Error object providing in a custom error name. This error name is then sent back to the client instead of the genreic "org.freedesktop.DBus.Failed" code

The smartmontools package contains two utility programs (smartctl and smartd) to control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA and SCSI hard disks. In many cases, these utilities will provide advanced warning of disk degradation and failure.

The suite of smartmontools contains two utilities:

smartctl is a command line utility designed to perform S.M.A.R.T. tasks such as disk self-checks, and to report the S.M.A.R.T. status of the disk.

smartd is a daemon that periodically monitors S.M.A.R.T. status and reports errors and changes in S.M.A.R.T. attributes to syslog.

Portage is probably Gentoos most notable innovation in software management. With its high flexibility and enormous amount of features it is frequently seen as the best software management tool available for Linux.
Portage is written in Python and Bash and therefore fully visible to the users as both are scripting languages.
Most users will work with Portage through the emerge tool. This chapter is not meant to duplicate the information available from the emerge man page. For a complete rundown of emerges options, please consult the man page.
Portage has several additional features that makes your Gentoo experience even better. Many of these features rely on certain software tools that improve performance, reliability, security, ...
To enable or disable certain Portage features you need to edit /etc/make.confs FEATURES variable which contains the various feature keywords, separated by white space. In several cases you will also need to install the additional tool on which the feature relies.
Not all features that Portage supports are listed here. For a full overview, please consult the make.conf man page.
Enhancements:
- FEATURES="confcache" integration; global caching to speed up configure calls, requires dev-util/confcache
- elog framework and accompanying modules for logging ebuild warnings, errors and general notices. Collects eerror/ewarn/elog/einfo messages.
- New elog function (should replace einfo in many cases) version syntax enhancements allowing multiple suffixes and a new cvs prefix for denoting "live sources" ebuilds.
- config files as directories enabling more flexible settings management.
- Addition of an register_die_hook method that allows ebuild/eclasses to register functions to be called for better debugging on errors.
- Addition of pre and post user hookable functions for each ebuild phase, accessible via portage bashrc. Example would be pre_src_unpack .
- cache refactoring- runtime improvement from 35% -> 65%.
- Intelligently handle and display USE_EXPAND-based IUSE variables.
- FEATURES="parallel-fetch". Download in parallel to compilation.
- Include a "changed or new" USE flag output when --verbose isnt specified.
- Support for splitting out debug information into separate files in /usr/lib{,32,64}.
- exec subsystem refactoring (now with less bugs!)
- Added sha256 and rmd160 hashes for digests/manifests
- Make --emptytree only apply to ${ROOT} rather than always including /.
- Allow packages to be upgraded that are only depended on via a "|| ( =cat/pkg-1* =cat/pkg-2* )" construct.
- Ebuild output is no longer cut off early when using PORT_LOGDIR.
- Distfiles indirection- $DISTFILES access goes through a tmp dir to fail access to files not listed in SRC_URI.
- Emerge now uses --resume to restart itself after portage upgrade.
- Atomic file updates via the new atomic_ofstream class.
- Global updates and fixpackages performance optimizations.
- Tests show that file locking is now more reliable.
- A bash call stack is printed when an ebuild dies in ebuild.sh.
- New rsync option handling by using a generic PORTAGE_RSYNC_EXTRA_OPTS variable
- Manifest2 support that will allow digest-* files to be eliminated from the tree.

WAchecker is a Python library for writing and executing automated and semi-automated Web accessibility tests.

Tests for Web Content Accessibility Guidelines 1.0 and Section 508 are included.