Free remedy software for linux

mod_auth_remedy is an Apache module for HTTP Basic authentication/authorization in the Remedy Action Request System (ARS).

Users of the Remedy Action Request System are organized in groups as in UNIX. Each user may belong to several groups. Users log into server using passwords. ARS stores information in so-called schemas, an analogue of tables in a relational database. Schemas have records.

There is a schema named User storing user information such as Login Name and Password, one record for each user. This schema corresponds to /etc/passwd on UNIX. Another schema named Group stores information about groups - it is for ARS what /etc/group is for UNIX.

On HTTP request to a constrained URL, the browser supplies Apache with username and password typed in the Basic authentication box. The module opens connection to the Remedy server RemedyServer as user RemedyBindName with password RemedyBindPass, and seeks the User schema for record with Login Name equal to the browser-supplied username.

Only if the record exists and contains password that matches the browser-supplied password, the module tells Apache to let the user in. If RemedyBindName directive is < None >, the module attempts to log onto Remedy staighfoward with browser-supplied username/password and if this login succeeds, it lets to access the URL.

The User schema record contains list of groups the user belongs to. This list is compared to the content of the standard Require group directive in the authorization phase.

Directives

The module supports the following run-time configuration directives:

RemedyAuthoritative (On|Off)
whether other modules will attempt authentication (Off) or not (On)
RemedyServer
Remedy Action Request System server machine name
RemedyBindName
Remedy user login under which Apache can connect to the Remedy server. This Remedy user should have read permissions on the Password field in the User schema. When set to , Apache will use the login supplied by browser, i. e. login typed in in the auth box.
RemedyBindPass
password of the Remedy user. Set to when the previous is set to
RemedyAPILog (On|Off)
enables intensive logging of module operations.

Jaggregate is a Java collections library that is modeled after the ANSI Smalltalk collection protocols.
It only works with J2SE 5.
Enhancements:
- A bug with SortedCollections produced by the zero-argument Collection.toSortedCollection() was fixed.
- Such collections could not be serialized, because the Comparator they use was not itself Serializable.
- This has been remedied.
- *From and *With methods were added to Dictionary and IdentityDictionary, despite compiler warnings about generic array creation.

Parse::RecDescent is a Perl module to generate Recursive-Descent Parsers.
SYNOPSIS
use Parse::RecDescent;
# Generate a parser from the specification in $grammar:
$parser = new Parse::RecDescent ($grammar);
# Generate a parser from the specification in $othergrammar
$anotherparser = new Parse::RecDescent ($othergrammar);
# Parse $text using rule startrule (which must be
# defined in $grammar):
$parser->startrule($text);
# Parse $text using rule otherrule (which must also
# be defined in $grammar):
$parser->otherrule($text);
# Change the universal token prefix pattern
# (the default is: s*):
$Parse::RecDescent::skip = [ t]+;
# Replace productions of existing rules (or create new ones)
# with the productions defined in $newgrammar:
$parser->Replace($newgrammar);
# Extend existing rules (or create new ones)
# by adding extra productions defined in $moregrammar:
$parser->Extend($moregrammar);
# Global flags (useful as command line arguments under -s):
$::RD_ERRORS # unless undefined, report fatal errors
$::RD_WARN # unless undefined, also report non-fatal problems
$::RD_HINT # if defined, also suggestion remedies
$::RD_TRACE # if defined, also trace parsers behaviour
$::RD_AUTOSTUB # if defined, generates "stubs" for undefined rules
$::RD_AUTOACTION # if defined, appends specified action to productions
Parse::RecDescent incrementally generates top-down recursive-descent text parsers from simple yacc-like grammar specifications.
Main features:
- Regular expressions or literal strings as terminals (tokens),
- Multiple (non-contiguous) productions for any rule,
- Repeated and optional subrules within productions,
- Full access to Perl within actions specified as part of the grammar,
- Simple automated error reporting during parser generation and parsing,
- The ability to commit to, uncommit to, or reject particular productions during a parse,
- The ability to pass data up and down the parse tree ("down" via subrule argument lists, "up" via subrule return values)
- Incremental extension of the parsing grammar (even during a parse),
- Precompilation of parser objects,
- User-definable reduce-reduce conflict resolution via "scoring" of matching productions.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

Asterisk Manager Suite (AMS) is a collection of software; an abstraction library called Asterisk Manager Interface (AMI), a proxy daemon called Asterisk Manager Proxy (AMP), and a gui client interface called Asterisk Manager Administrator (AMA).
The intention of the software is to make management and administration of the Asterisk Open Source PBX easier. The software is currently targetted at corporate environments with call centers but plans for further expansion exist.
The C library, libami (AMI) is intended to make executing commands through Asterisks Manager Interface easier. The library is used extensively in both AMP and AMA, although you could use it in your own software as well.
The proxy daemon is intended to remedy an outstanding issue with Asterisks Manager Interface: The interface does not deal well with excessive connections. To get around this, a proxy is a suitable solution. As well as simply being a proxy, AMP has other functions as well, including recording statistics and activities of call center agents.
AMA is intended to be a gtk application for monitoring and administrating an Asterisk server. AMA requires AMP for connectivity and has many functions as well as some planned in the future. AMA was first inspired by Asterisks own gastman client, which was well done, but to small to be of any real use to anyone in a corporate environment except perhaps admins.
Enhancements:
- Minor bugfixes dealing with ampd not sending events properly.

This program allows you to visualise the power levels in each frame of an MP3 file, select a number of frames, cut out frames you dont want, and then save the selected frames (excluding the cuts) to a separate MP3 file.
Note: If the input MP3 stream uses the bit reservoir (and most do), then the first frame in the selection will be incomplete, as it depends on the previous frame in the stream. You will get some problems on playback. If you disable the bit reservoir when encoding (e.g use --nores with Lame), then this isnt a problem.
This is my first GUI program ever, and Ive only tested it on FreeBSD 3.x and Mandrake Linux 6.0. To install the application, you will need:
GTK+ 1.2
Autoconf
Automake
GNU Make
mpg123 to play a selection
Running mpcut will bring up a window with a white rectangle to display the frame powerlevels. You can either open a file by naming it on the command-line, or by using File->Open by the drop-down menus.
After opening an MP3 file, you will see a plot of frame power vs frame number in the display area. The frame numbers are shown on the horizontal scale above the display area. Use the mouse and click-drag to select a region, which will be displayed in red. A single-click will deselect the region.
Note: there is no visual feedback when performing mouse drags. A future version will remedy this omission.
If you click-drag from within the selected region and drag outside the region, the new area is added to the selection. If you click-drag from outside the selected region and drag into the region, parts of the selection will be removed.
You can do Edit->Select All to select the whole file, or Edit->Unselect All to clear the selection.
You can also set a marker by doing a single middle-click. The marker is shown as a vertical blue line. If you then do a middle-button mouse drag, the marker sets the start of a selection, and the end of the drag sets the endpoint of the selection.
You can `cut out a selected area by using the `c key. The frames will be greyed out in the display area, but they will never be played or saved to your save file. You can remove all the cuts you have made with the `r key. You can undo the last cut by using the ctrl-Z keystroke.
Enhancements:
- Added ctrl-Z function to undo the last cut. Fixed bug: cuts are cleared when a file is opened.

ChiliMac is an interactive macro language implemented in 100% Java. It emphasizes ease of use and portability, while still providing several features for the power user.

It is built around XML (eXtensible Markup Language), which is a vibrant industry standard. This ensures compatibility with several third party tools and remarkable flexibility.

ChiliMac processes source documents, performs the specified actions and then generates output from the processed source documents.

Installation:

ChiliMac currently lacks an automated installation procedure. This will be remedied in future versions. Until then, the following should serve as a guide to manual installation of ChiliMac.
Firstly, you must install a Java Standard Edition Runtime Environment 5.0 (1.5.0) or greater.

Next, you will need to download the ChiliMac binary (the JAR file) to a suitable location for your system. Finally, the tricky part, you have to manually integrate the ChiliMac binary into your system.

This varies greatly from system to system, but is generally achieved by creating a shell script or batch file and adding it to your systems path.

Alternatively, you can just run the ChiliMac binary from the command line as follows (where x.y.z is substituded with the actual version number of the JAR file):

java -jar chilimac-x.y.z-bin.jar

CPOINt is a new way to create slideshows that can be viewed on many different operating systems. Most slideshow creating programs (not mentioning any names) are designed to only work with the operating system that they were created on. Some effort has been made to remedy this, but there are no fully cross platform solutions.
One of CPOINts purposes is to create a new type of slideshow that can be viewed on older computers and newer. The software is split into three projects: A light viewer, which can run on older machines such as pentiums and 486s. A "heavy" viewer for the newest computers, with all the animations and special effects you could need. And finally, a GTK based WYSIWYG editor.
Enhancements:
- Button and font support was fixed, and an autotools-based package and a Debian Etch package have been created.
- Support for default fonts was added, a bug was fixed in the CString library, and the rest of the source code has been added to the archive.