Ports Search

Libcompizconfig is an alternative configuration system for compiz and provides the following features: - Automatic plugin list generation. - Import/Export of the current configuration. - Configuration profiles. - Parsing of Compiz metadata files to provide an easy to use API for configuration managers. - Conflict handling for plugins and actions. - Support for different configuration storage backends. - Desktop environment integration. If a backend provides desktop environment integration, then Compiz will share the keybindings and settings with the default desktop environment window manager like metacity or kwin. - Its own Compiz configuration plugin "ccp" to provide all features of libcompizconfig with compiz.

A Simple Python/GTK based settings manager for the CompizConfig system

Basic GUI for Microsoft's Media Transfer Protocol (MTP) including file transer and some playlist handling.

This module provide easy interface to make MIME::Lite object with html formatted mail.

MIME::Lite::TT is the wrapper of MIME::Lite which enabled Template::Toolkit as a template of email.

This module collects IP validation routines to make input validation, and untainting easier and more readable. All functions return an untainted value if the test passes, and undef if it fails. This means that you should always check for a defined status explicitly. Don't assume the return will be true. (e.g. is_username('0')) The value to test is always the first (and often only) argument.

This module collects common URI validation routines to make input validation, and untainting easier and more readable. All functions return an untainted value if the test passes, and undef if it fails. This means that you should always check for a defined status explicitly. Don't assume the return will be true. The value to test is always the first (and often only) argument. There are a number of other URI validation modules out there as well. This one focuses on being fast, lightweight, and relatively 'real-world'. i.e. it's good if you want to check user input, and don't need to parse out the URI/URL into chunks. Right now the module focuses on HTTP URIs, since they're arguably the most common.

The package consists of two programs - PortRedorector and PortTest. PortRedirector is a daemon that runs telnet to the remote port of the terminal server and redirects its input and output to a virtual terminal device (/dev/pty*). The corresponding slave device (dev/tty*) then can be used by an application that expects a local async terminal port. For example, to monitor a UPS (connected to AUX ports on a Cisco router) using nut. Whenever telnet subprocess terminates on any reason, it is restarted as soon as any data received from the terminal device. It can also work when authentication is required, i.e. it can pass username and password specified in its configuration file. PortTest is something like cu(1). You can use either of them to test the connection.

The libevent API provides a mechanism to execute a callback function when a specific event occurs on a file descriptor or after a timeout has been reached. Furthermore, libevent also support callbacks due to signals or regular timeouts. libevent is meant to replace the event loop found in event driven network servers. An application just needs to call event_dispatch() and then add or remove events dynamically without having to change the event loop. Currently, libevent supports /dev/poll, kqueue(2), event ports, select(2), poll(2) and epoll(4). The internal event mechanism is completely independent of the exposed event API, and a simple update of libevent can provide new functionality without having to redesign the applications. As a result, Libevent allows for portable application development and provides the most scalable event notification mechanism available on an operating system. Libevent can also be used for multi-threaded applications.

GNU Pth - The GNU Portable Threads Copyright (c) 1999-2005 Ralf S. Engelschall <rse@gnu.org> Pth is a very portable POSIX/ANSI-C based library for Unix platforms which provides non-preemptive priority-based scheduling for multiple threads of execution (aka ``multithreading'') inside event-driven applications. All threads run in the same address space of the server application, but each thread has it's own individual program-counter, run-time stack, signal mask and errno variable. The thread scheduling itself is done in a cooperative way, i.e., the threads are managed by a priority- and event-based non-preemptive scheduler. The intention is that this way one can achieve better portability and run-time performance than with preemptive scheduling. The event facility allows threads to wait until various types of events occur, including pending I/O on file descriptors, asynchronous signals, elapsed timers, pending I/O on message ports, thread and process termination, and even customized callback functions.