Free watcher software for linux

ps-watcher monitors various processes based on ps-like information. ps-watcher runs the ps command periodically and triggers commands on matches.
The match patterns are Perl regular expressions which can refer to the process information via variables.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- Some minimal Cygwin support was added, and support for other operating systems (NetBSD, OpenBSD, and OS X) was corrected.
- For security, there is aa --path option to limit the path used in running commands.
- Some bugs were fixed and the code was modernized a little.

Google Reader Watcher is a Firefox extension that will check your Google Reader for unread feeds and if you have, the plugin will display them on your browsers statusbar.

mswatch project is a command line unix program that keeps two mailboxes synchronized more efficiently and with shorter delays than periodically synchronizing the two mailboxes.
mswatch watches mailboxes to know when to initiate mailbox syncs. Using mswatch, your mail synchronization program can be called on demand instead of through polling, resulting in prompter mail delivery and lower bandwidth usage and server load.
mswatch is designed to work in conjunction with mailbox synchronization programs, currently supports watching Linux (2.4+) hosted Maildirs (including Maildir folders, Maildir++), and is licensed under the GNU GPL. Future support for additional mailbox formats, especially for mbox, is planned.
Why mswatch
Keeping a set of mailboxes on multiple computers means keeping the copies synchronized (eg on ones desktop and laptop or on a personal computer that can not be reached while on the road an always-reachable server). While the IMAP protocol is designed to support this and is widely used, IMAP clients can only detect mailbox changes by querying the server.
Thus clients generally either sync when the user requests or sync periodically. However, because each mailbox sync uses server and network resources and because users often have a number of mailboxes, many of which receive mail infrequently, one must compromise between prompt message delivery and low server and network resource usage. Typical practice is to sync only when the user requests or to sync periodically with 5-10 minute frequencies. Nonetheless, it is often helpful for users to see new mail fairly soon after its arrival (eg notifications, group meeting changes, or active conversation threads).
mswatch addresses this speed of delivery vs resource usage tradeoff using interrupt-based instead of polling behavior to detect mailbox changes. mswatch asks each of the two mailstores to send mailbox change notifications; when mswatch receives a notification it in turn invokes the users mailbox synchronization program for the changed mailbox. Thus, idle mailboxes do not use active resources and prompt mailbox synchronization is efficient.
Version restrictions:
- Because mswatch abstracts mail changes and synchronization to the mailbox (instead of message) level and because mail watcher communication is one-way, extra mailbox syncs occur. While it would be great to avoid this extra work, it is in the noise compared to the number of empty syncs that polling accumulates.
For example, the case of new mail delivered to the mail servers INBOX:
(1) mswatch detects the changed server INBOX
(2) mswatch invokes the mail syncer for INBOX, which adds the mail to the local INBOX
(3) mswatch detects the changed local INBOX
(4) mswatch invokes the mail syncer for INBOX, which detects no changes
Thus two syncs occur in this case instead of the single necessary sync.
Enhancements:
- Per-mailbox inter-sync delays were added to rarely sync high volume mailboxes and quickly sync important mailboxes.
- Inter-sync delays are allowed to be greater than the maximum error delay.
- mswatch now prints the names of pending mailboxes upon receiving SIGUSR1.

Gtk2::Helper is a Perl module for convenience functions for the Gtk2 module.

SYNOPSIS

use Gtk2::Helper;

# Handle I/O watchers easily, like Gtk 1.x did
$tag = Gtk2::Helper->add_watch ( $fd, $cond, $callback, $data )
$rc = Gtk2::Helper->remove_watch ( $tag )

ABSTRACT

This module collects Gtk2 helper functions, which should make implementing some common tasks easier.

Gtk2::Helper->add_watch ( ... )

$tag = Gtk2::Helper->add_watch ( $fd, $cond, $callback, $data )

This method is a wrapper for Glib::IO->add_watch. The callback is called every time when its safe to read from or write to the watched filehandle.

$fd

Unix file descriptor to be watched. If you use the FileHandle module you get this value from the FileHandle->fileno() method.

$cond

May be either in or out, depending if you want to read from the filehandle (in) or write to it (out).

$callback

A subroutine reference or closure, which is called, if you can safely operate on the filehandle, without the risk of blocking your application, because the filehandle is not ready for reading resp. writing.

But aware: you should not use Perls builtin read and write functions here because these operate always with buffered I/O. Use low level sysread() and syswrite() instead. Otherwise Perl may read more data into its internal buffer as your callback actually consumes. But Glib wont call the callback on data which is already in Perls buffer, only when events on the the underlying Unix file descriptor occur.

The callback subroutine should return always true. Two signal watchers are connected internally (the I/O watcher, and a HUP watcher, which is called on eof() or other exceptions). Returning false from a watcher callback, removes the correspondent watcher automatically. Because we have two watchers internally, only one of them is removed, but probably not both. So always return true and use Gtk2::Helper->remove_watch to disable a watcher, which was installed with Gtk2::Helper->add_watch.

(Gtk2::Helper could circumvent this by wrapping your callback with a closure returning always true. But why adding another level of indirection if writing a simple "1;" at the end of your callback solves this problem? ;)

$data

This data is passed to the callback.

$tag

The method returns a tag which represents the created watcher. Later you need to pass this tag to Gtk2::Helper->remove_watch to remove the watcher.

Adept project is a GUI to the Advanced Packaging Tool for KDE. Adept is developed by Peter Rockai and is sponsored by Canonical Ltd. through the Kubuntu project.
Main features:
- package list with customisable filters
- debtags-based drag&drop filtering
- package browser with package relations, file list and detailed info about package
- currently rather rough sources.list editor
- download, installation progress meters
- change review, status toolbar
- simplified interface for system upgrades: adept updater
- simplified interface for application management: adept installer
- system-tray update notification icon: adept notifier
Enhancements:
- Removed apt-index-watcher dependancy, dropped in debian.
- Fix build order in adept/Makefile.am and kubuntu_upgrader/Makefile.am
- Enable simple-patchsys.mk in debian/rules.

Scroll Rack is a virtual tabletop on which you can play card games against other people over a network.
Scroll Rack was designed to simulate the Magic: The Gathering (R) game, but it can be expanded to simulate other games.
It supports two-player peer-to-peer mode, and client/server mode for multi-player games and tournaments.
Main features:
- Open source.
- Support planned for Linux, Mac, and Windows.
- Can download card images from www.wizards.com and display them on the virtual tabletop.
- Clients can connect directly (peer-to-peer) or through a server run by a third party.
- Peer-to-peer games use encryption to prevent players from seeing cards they arent allowed to see.
- Peer-to-peer games use Jabber so both players can be behind firewalls.
- Client/server games support any number of players and watchers.
- Supports Living Wish (move card from sideboard to hand).
- Supports Battle of Wits (very large decks).
Enhancements:
- Add Deck Editor.
- Download card images from magiccards.info instead of wizards.com. Higher quality images.
- Download Oracle spoiler file from a Scroll Rack dedicated site instead of gatherer.wizards.com. Faster, more reliable download, with more data.
- Rearrange files in .scrollrack.cache.
- Add Save Log menu item.
- When starting a game with a sideboarded deck, show note in New Game dialog.

Relations::Display is a DBI/DBD::mysql Query Graphing Perl module.

SYNOPSIS

# DBI, Relations::Display Script that creates a
# matrix, table, and graph from a query.

use DBI;
use Relations;
use Relations::Query;
use Relations::Abstract;
use Relations::Display;

$dsn = "DBI:mysql:watcher";

$username = "root";
$password = ;

$dbh = DBI->connect($dsn,$username,$password,{PrintError => 1, RaiseError => 0});

$abstract = new Relations::Abstract($dbh);

$display = new Relations::Display(-abstract => $abstract,
-query => {-select => {total => "count(*)",
first => "Bird",
second => "Count",
third => "if(gender=Male,Boy,Girl)",
tao => "if(gender=Male,Yang,Yin)",
sex => "gender",
kind => "sp_name",
id => "species.sp_id",
fourth => "(species.sp_id+50)",
vert => "2",
horiz => "1.5"},
-from => [bird,species],
-where => [species.sp_id=bird.sp_id,
species.sp_id < 4],
-group_by => [sp_name,gender,first,second],
-order_by => [gender,sp_name]},
-x_axis => first,kind,id,fourth,
-legend => second,third,tao,sex,vert,horiz,
-y_axis => total,
-hide => fourth,third,vert,horiz,
-vertical => vert,
-horizontal => horiz);

$matrix = $display->get_matrix();

$table = $display->get_table();

$display->set(-chart => bars,
-width => 400,
-height => 400,
-settings => {y_min_value => 0,
y_max_value => 3,
y_tick_number => 3,
transparent => 0}
);

$gph = $display->get_graph();

$gd = $gph->gd();

open(IMG, >test.png) or die $!;
binmode IMG;
print IMG $gd->png;

$dbh->disconnect();

Event is an Event loop processing.

SYNOPSIS

use Event qw(loop unloop);

# initialize application
Event->flavor(attribute => value, ...);

my $ret = loop();

# and some callback will call
unloop(ok);

The Event module provide a central facility to watch for various types of events and invoke a callback when these events occur. The idea is to delay the handling of events so that they may be dispatched in priority order when it is safe for callbacks to execute.

Events (in the ordinary sense of the word) are detected by watchers, which reify them as events (in the special Event module sense). For clarity, the former type of events may be called "source events", and the latter "target events". Source events, such as signals arriving, happen whether or not they are being watched. If a source event occurs which a watcher is actively watching then the watcher generates a corresponding target event. Target events are only created by watchers. If several watchers are interested in the same source event then each will generate their own target event. Hence, any particular source event may result in zero, one, two, or any number of target events: the same as the number of watchers which were actively watching for it.

Target events are queued to be processed in priority order (priority being determined by the creating watcher) and in FIFO order among events of the same priority. Queued ("pending") events can, in some cases, be cancelled before being processed. A queued event is processed by being passed to the callback function (or method on a particular object or class) which was specified to the watcher.

A watcher, once created, operates autonomously without the Event user having to retain any reference to it. However, keeping a reference makes it possible to modify most of the watchers characteristics. A watcher can be switched between active and inactive states. When inactive, it does not generate target events.

Some types of source event are not reified as target events immediately. Signals received, for example, are counted initially. The counted signals are reified at certain execution points. Hence, signal events may be processed out of order, and if handled carelessly, on the wrong side of a state change in event handling. A useful way to view this is that occurrence of the source event is not actually the arrival of the signal but is triggered by the counting of the signal.
Reification can be forced when necessary. The schedule on which some other events are created is non-obvious. This is especially the case with watchers that watch for a condition rather than an event. In some cases, target events are generated on a schedule that depends on the operation of the event loop.