Free tv program software for linux

Program D is the most widely used free ("open source") AIML bot platform in the world. Program D project is the most feature-complete, best-tested implementation of the current AIML specification.
It supports unlimited multiple bots in a single server instance, and has an open-ended architecture for interacting via any interface imaginable. The standard release provides a J2EE web application implementation that can be deployed as a .war file. Drop-in listeners are available for IRC, ICQ/AIM, and Yahoo.
It includes an automated testing framework for testing knowledge bases, and is packaged with an AIML Test Suite that verifies that the program itself complies to the AIML specification.
Program D is known to work with many different languages / character sets.
Its component-oriented architecture allows it to be integrated into any application framework desirable. It is implemented in Java, and uses many features of the latest JDK to provide optimum code reliability. It is actively maintained and supported.
Enhancements:
- This is a highly-recommended release which introduces some interesting performance improvements, fixes a number of important bugs, and brings some major architectural improvements.
- Most notably, Program D can now be deployed as a .war file to a Web application server, and can interact with a Web client using "AJAX" technologies.
- This final release follows three release candidates which ironed out a few minor issues.

TVProg project is a TV guide software.

TVProg is TV guide software running as a Web server application. It fetches the TV guide source from tvmovie.de and stores it in a MySQL database.

TV shows can be browsed online. Theres also a vcr wrapper script that, running as a cron job, is able to record scheduled tv shows in DivX.

The TVProg package contains a script "list.cgi" that is run as a CGI script to browse the tv guide. You can select channels, do searches or look what is running right now. Theres a detail view for every single tv show.

Cookies are supported for keeping the view properties while browsing.

A cron job script, "vcrwrapper.pl", acts as a wrapper for vcr. Run it every minute and you will have a nice frontend for vcr: In the tv show detail view you can click the record link to schedule it for recording.

There is also a "profile" section where users can subscribe to receive daily tvshow mailings. Also, a user may activate a search, done by a cron job, and receive the search results via email.

This way you can look for a special tvshow or movie without having to look into the listings every day.

game control program project helps administrate game servers, especially automated kicking of players.
game control program helps you administrate gameservers (its written for Q1 and Q3, but works for others). It is highly modular and therefore extensible.
With the current modules, it can start/stop servers, create and rotate logfiles, allow remote administration via telnet, and kick misbehaving players automagically (according to a rule set).
Main features:
- starting a game server and getting hold of all log messages
- creating log files (complete or rotated per map)
- parsing log messages (game independent and configurable)
- sophisticated remote administration (user groups, extensible command set)
- sending commands to a running server (Q,QW,Q2,Q3)
- automatic kicking system according to specific rules (eg. too high rate set by the client)
- check if a server is hanging and kill the process to force a restart
- sending commands to the server at specified timesallows timed startup / shutdown of servers
Enhancements:
- renamed packages and modules (see doc/config)
- added new module: CommandScheduler
- sends a command to the server in defineable periods - see cfg/events.xml allows:
- COMMAND - send as RCon command (command is set as attribute parameter)
- KILLSERVER
- STARTUP
- SHUTDOWN

Program Guard allows the user of a Linux workstation to specify which application programs that are allowed TCP/IP connections to the Internet (Internet addresses are defined as any IP address not in the range of 10.0.0.0/24 or 192.168.0.0/16).

The application program names can be specified by listing them in a file (Static Mode) by querying the user (Query Mode). In Query Mode, when a program that is unknown to Program Guard attempts to access an Internet IP address, Program Guard displays the Program Guard Dialog Box.

In addition to providing connection information, this dialog box gives the workstation user the option of allowing the program to access the Internet or to be blocked from accessing the Internet. This can be done either for the current instance of the program or for this and all future instances of the program (Make Persistent checkbox).

Currently, the program names that are allowed or denied Internet access apply to all users of the workstation rather than on a per user basis. For example, if Program Guard is running in Query Mode and user A invokes a program previously blocked from Internet access by user B, the program will be blocked from Internet access for User A as well.

Connections blocked by Program Guard are logged to the Program Guard log file pgrd.log. It is located in the /var/log/pgrd directory. If desired, Program Guard can be configured to log all Internet connection attempts rather than just those that have been blocked.

Program Guard was tested on Fedora Core 1 and Fedora Core 3 on single processor 32 bit X86 Intel processors. It has not been tested on other distributions or on multi-processor machines. While it works on Fedora Core 1, it will not build on a standard Linux 2.4.x kernel due to task_struct definitions that were not made until Linux 2.6. If there is enough interest, a version that runs under a standard Linux 2.4 kernel may be made available.

To run in Query Mode, Gnome 2.x and Glade 2.x are required. There are no prerequisites for Static Mode.

Installation:

Program Guard consists of three components: a kernel module; a daemon; and a Gnome GUI user interface component. All files needed to build the components are in the pgrd.tgz file. An installation shell script install-pgrd is provided for Fedora distributions.

It will build/install (or remove) the kernel module and daemon as well as configure them to be started automatically when the system is booted. To invoke it, type install-pgrd < install | remove >. This script may or may not be useable as is for other Linux distributions.

If you modify the install script, please note that the module, daemon and various support files must be installed in the /opt/pgrd directory for Program Guard to work properly (this is already handled when using the install script as provided). To run in Query Mode, each user must be configured by invoking the install-pgrd_user < username > script. And by going to the Preferences->More Preferences->Sessions selection in the Fedora Main Menu and adding pgrdgui to the Startup Programs tab.

Program Guard will be started the next time the machine is rebooted. If you do not wish to reboot, you may start Program Guard manually as described below in Manual Starting And Stopping. Note: If starting manually and using Query Mode, once the daemon and kernel module are started, make sure that you log out and log back in.

Sample Inventory Program provides a laboratory inventory management system (LIMS) for Zope.
Many integration tests exist for various aspects of the SIP application, ranging from command line importing of samples and project configuration to CSV Web-based importing of sample modifications.
Main features:
- Cross platform using the Zope 3 appliation server and Python language. Contains over 200 unit and integrations tests.
- Command line import functionality (import application configuration, projects, samples, aliquots and container heirarchies)
- Cross project searches based on Subject Ids, Other Ids, Additional Sample Data, and Sample Types. Uses REPORT Permission.
- Search Form Screenshot
- Project level permissions. Users can be enabled/disabled by removing User Permission in the Applicaiton root. Lab Technician Permission allows users to put contents into a shipment and add/modify Samples. Project Manager permission allows project configuration as well as administering Users for specified projects.
- User and Permission Screenshot
- 100% Web based interface (IE, Mozilla, Safari tested). QT based client in development.
- Projects Overview Screenshot
- Ability to Split Aliquots into smaller units and put them into separate physical containers.
- Ability to Derive Aliquots into other Sample Types. Derived Samples/Aliquots links to their origin sample.
- Locations/Containers are heirarchical and can be restricted to a Project
- Shipments act as virtual containers where Lab Technicans can split aliquots into. AlsocShipments contain Contact Info, Shipping Info and Funding Info. While the Shipment Status will control the status of the Shipment moving from: Incomplete, In-Transit, and finally Received based on date fields being filled out.
- Shipment Screenshot
- Understandable relational model that enables simple reporting to be easily constructed by third party tools such as Jasper Reports
- Batch editing available using CSV files. All changes are transactional. You can easily import hundreds of samples into multiple projects by using CSV files and importing them through the web interface. You can change locations of aliquots by using the CSV import functionality. Any functionality that can be done in the web interface is complimented by CSV functionality.
- Project Search Results Screenshot
- Ability to administer Sample Type, Container Type, Locations and Unit of Measure at the application level to enforce standards across all Projects. Requires Application Manager permission.
- Ability to assign Sample Type, Locations, Technicans in a Project by Project basis.
- Project Administration Screenshot
- Advance Attribute Capture forms enable Project Administrators to specify what attributes for their Sample Types need to be captured for their project. Now non-technical users can ensure that Lab Technicans capture any attribute for any Sample Type. Attributes are limited to: DateTime, Boolean, Float, Integer, String and Text fields. Default Values can be assigned.
- Sample Type Attributes Screenshot
- Finally Sample Type Attributes can have validation scripted on a field by field basis. By using the TALES Validation functionality for Sample Type Attribute Fields. Examples of TALES validation:
- python: value < 100 # value of the field is less than 100
- python: value < datetime.date(2006, 10, 31)
- # value of the field is less than 10/31/2006
- Edit Comments will require a comment to be added to any field that is edited. These are used in conjunction with RDBMS triggers to keep a audit log to ensure that all changes to all inventory can be tracked.