Free express personnel software for linux

SIP Express Router (ser) is a high-performance, configurable, free SIP ( RFC3261 ) server .
SER features an application-server interface, presence support, SMS gateway, SIMPLE2Jabber gateway, RADIUS/syslog accounting and authorization, server status monitoring, FCP security, etc. Web-based user provisioning, serweb, available.
Its performance allows it to deal with operational burdens, such as broken network components, attacks, power-up reboots and rapidly growing user population.
SERs configuration ability meets needs of a whole range of scenarios including small-office use, enterprise PBX replacements and carrier services.
Main features:
- accounting
- digest authentication
- CPL scripts
- ENUM support
- instant messaging
- MySQL support
- PostgreSQL support
- a presence agent
- Radius authentication and accounting
- Diameter authentication
- record routing
- SMS gateway
- Jabber gateway
- NAT traversal support transaction module
- registrar
- user location
SER has been extensively and successfuly tested with many SIP products from other vendors (Microsoft, Cisco, Mitel, snom, Pingtel, Siemens, and many others). It has been powering our SIP services continuously for more than two years.

American Express Expense Report to QIF Converter project is a utility that converts American Express expense reports into QIF.
There are three main reasons:
1. American Express only offers QIF files for the last 6 months of activity whereas the expense reports go back 2 years. You can also run a report with a custom 1- to 12-month time period within 24 months of the current calendar month.
2. American Express QIF files have limited to no "categorization" whereas the expense report categorizes each transaction with a "Merchant Category" and "Subcategory".
3. American Express QIF files do not indicate which credit card in a multi-card account performed the transaction.
Main features:
- Inserts card owner and last 5 digits of the credit card in the memo field
- Reads config file for user defined rules so transactions can be automatically mapped to different accounts in your accounting software. Mapping can be based on:
- Credit card owner
- Vendor name
- AMEX "Merchant Category" and "Subcategory"
- Any combination of the above
- Sanitizes and cleans up vendor names
- Has the ability to add a prefix to all vendor names

Class::Meta::Express is a Perl module for concise, expressive creation of Class::Meta classes.

Synopsis

package My::Contact;
use Class::Meta::Express;

class {
meta contact => ( default_type => string );
has name;
has contact => ( required => 1 );
}

This module provides an interface to concisely yet expressively create classes with Class::Meta. Although I am of course fond of Class::Meta, Ive never been overly thrilled with its interface for creating classes:

package My::Thingy;
use Class::Meta;

BEGIN {
# Create a Class::Meta object for this class.
my $cm = Class::Meta->new( key => thingy );

# Add a constructor.
$cm->add_constructor( name => new );

# Add a couple of attributes with generated accessors.
$cm->add_attribute(
name => id,
is => integer,
required => 1,
);

$cm->add_attribute(
name => name,
is => string,
required => 1,
);

$cm->add_attribute(
name => age,
is => integer,
);

# Add a custom method.
$cm->add_method(
name => chk_pass,
code => sub { return code },
);
$cm->build;
}

This example is relatively simple; it can get a lot more verbose. But even still, all of the method calls were annoying. I mean, whoever thought of using an object oriented interface for declaring a class? (Oh yeah: I did.) I wasnt alone in wanting a more declarative interface; Curtis Poe, with my blessing, created Class::Meta::Declare, which would use this syntax to create the same class:

package My::Thingy;
use Class::Meta::Declare :all;

Class::Meta::Declare->new(
# Create a Class::Meta object for this class.
meta => [
key => thingy,
],
# Add a constructor.
constructors => [
new => { }
],
# Add a couple of attributes with generated accessors.
attributes => [
id => {
type => $TYPE_INTEGER,
required => 1,
},
name => {
required => 1,
type => $TYPE_STRING,
},
age => { type => $TYPE_INTEGER, },
],
# Add a custom method.
methods => [
chk_pass => {
code => sub { return code },
}
]
);

This approach has the advantage of being a bit more concise, and it is declarative, but I find all of the indentation levels annoying; its hard for me to figure out where I am, especially if I have to define a lot of attributes. And finally, everything is a string with this syntax, except for those ugly read-only scalars such as $TYPE_INTEGER. So I cant easily tell where one attribute ends and the next one starts. Bleh.

This project is to produce drivers for the Logitech Quickam Express that will run popular linux software, such as video for linux.

This site hosts the Linux driver for the QuickCam Express and other QuickCam-related and QuickCam-compatible USB web cameras. The original work was done by Georg Acher and was known as qce-ga; Jean-Frederic Clere took that driver and created the first Video4Linux (V4L) driver, enabling popular V4L applications such as Xawtv to display pictures from the webcam. Since then, a group of developers around the world have evolved the driver into its current state, adding support for new cameras and chipsets as they have become available. In the process, the driver became known as qc-usb to reflect the fact that it supports a wide variety of USB-attached QuickCam cameras, not just the QuickCam Express.

The qc-usb driver supports the following webcams:

Dexxa Webcam
Labtec Webcam (old model)
LegoCam
Logitech QuickCam Express (old model)
Logitech QuickCam Notebook (some models)
Logitech QuickCam Web

Generally, any USB camera with a USB vendor ID of 0x46d and a USB product ID of 0x840, 0x850, or 0x870 (so, 0x46d:0x840, for example), should work. You can see the USB ID using operating system utilities such as lsusb in Linux.

Bridging the worlds of NNTP clients and RSS feeds, nntp//rss is an application that will enable you to use your existing favorit. nntp//rss works like a bridge between RSS feeds and NNTP clients, the content extracted being read by the NNTP newsreader. RSS feeds are represented as NNTP newsgroups, providing a simple, straightforward and familiar environment for news reading. nntp//rss contains both an NNTP server and an RSS aggregator, with a web interface for administration and monitoring. Installation is as simple as unpacking the distribution and running the application. It has been tested against popular NNTP newsreaders, including Mozilla, Outlook Express, MT-NewsWatcher, Free Agent, and text-based readers such as Gnus, tin and nn.

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....