Free connections tickets software for linux

QoS Connection Tuning HOWTO is a document which explains how to tune network connection performance.

This enables you to get the maximum benefit out of your connection without lag and loss.

Net::Connection::Sniffer can gather stats on network connections.

SYNOPSIS

use Net::Connection::Sniffer;
gather($config)
__top

Net::Connection::Sniffer is a perl module to gather connection statistics by listening to ethernet traffic. Traffic is filtered using standard BPF notation as described in the tcpdump documentation and implemented using the standard pcap library to sniff packets on host network interfaces.

phpMysqlConnection provides a PHP class for handling MySQL database connections.
phpMysqlConnection is an interface class to be used with the PHP programming language to help projects connect to a MySQL database server and perform queries.
The methods of this class prevent the programmer from having to memorize all the different steps needed to connect to the database, perform a query, and retrieve results.
Enhancements:
- A function to return XML-formatted data record sets from queries has been added.

dl Download Ticket Service project is a minimalist and rough download ticket service with automatic expiration, written in PHP. Ive been using this service as an email-attachment replacement for my company, but there are no plans on extending it. It will remain minimal: no fancy features, just bug fixes.
Installation:
Copy the "htdocs" directory to a directory of choice under your web server. Configure the needed parameters inside "include/config.php" to reflect the external url, main password, etc. The "include" directory must not be accessible: if you use apache, the included .htaccess file should be sufficient; consult your web server documentation otherwise.
A spool directory outside of the web server root must be accessible to the web server process. In the example "include/config.php" this is configured as "/var/spool/dl". If you web server runs as "nobody:nogroup", issue:
mkdir -p -m770 /var/spool/dl
chgrp nogroup /var/spool/dl
to create correctly this directory.
The maximal upload limit is determined by several PHP configuration parameters:
file_uploads: must be "On".
upload_tmp_dir: ensure enough space is available.
upload_max_filesize: change as needed.
post_max_size: must be at least 1M larger than upload_max_filesize.
The upload limit as shown in the submission form is determined automatically from the upload_max_filesize parameter. You can also set these parameters with ini_set() inside "include/config.php" or through apaches directives to localize them to the installation path.
There are several bugs in the dba_open() function in PHP 4.x which cannot be fixed. If you can, upgrade PHP to at least 4.3.5. If you cannot upgrade, you need to configure the "$dbHandler" parameter to something available to your PHP installation (usually db3/db2/dbm) and use the Berkeleys DB "db4_load" utility to create an empty database:
echo | db4_load /var/spool/dl/data.db
echo | db4_load /var/spool/dl/user.db
chmod 770 /var/spool/dl/*.db
chgrp nogroup /var/spool/dl/*.db
Depending on your system, you may have to use "db3_load/db2_load/etc" instead of "db4_load". Sometimes these utilities are part of "db*-util" packages under several linux distributions. If you have PHP 4.3.5 or greater, this is done automatically.
Ticket expiration is performed automatically when any web page is requested. This means that expired downloads will still occupy space on the spool directory until a web page is first serviced. If you need to ensure that the spool is purged regularly (for very low traffic servers), setup a scheduled job that requests the "http://dl.example.com/d/" page. Under UNIX, setup a cron entry like this:
0 0 * * * wget -q -O /dev/null "http://dl.example.com/d/" > /dev/null
Version restrictions:
- Tested with all mayor and minor browsers.
- Tested with PHP 4.2/4.3.
- Byte ranges are currently not supported.
- The submit button is not disabled correctly with Internet Explorer 6 (works on other graphical browsers however).

Net::FreeDB2::Connection is a FreeDB/CDDB abstract connection class.

Net::FreeDB2::Connection is an abstract class to represent connections to FreeDB/CDDB servers. After a successfull connection, FreeDB/CDDB queries, reads etc can be made to obtain/provide information from/to FreeDB/CDDB databases.

CONSTRUCTOR

new (OPT_HASH_REF)

Creates a new Net::FreeDB2::Connection object. By default connect () is called to initiate the connection but see option no_connect. See the implementation for complements/restrictions.

Options for OPT_HASH_REF may include:

client_name

Mandatory option to name the connecting client software.

client_version

Mandatory option with the client software version string.

client_host

The hostname of the client. Defaults to &Sys::Hostname::hostname ().

client_user

The user of the client. Defaults to scalar (getpwuid ($>));

freedb_host

The FreeDB/CDDB host. Defaults to freedb.freedb.org.

freedb_port

The port on the FreeDB/CDDB host.

proxy_host

Proxy host.

proxy_port

Port on the proxy host. Defaults to 8080.

proxy_user

Proxy user name to use.

proxy_passwd

Proxy password to use.

no_connect

Do not call connect () during instanciation.

EZ-Ticket provides a multi-user, Web-based ticket/issue tracking system.
EZ-Ticket is a Web-based ticket tracking system, built with simplicity in mind. Unlike other ticket systems, this ticket system has the same functionality that other ticket systems have, without all the complexity, making its use efficient and effective.
INSTALL:
-Unpack the tar file in your document root
-Make sure php is enabled
-use a web browser to hit doc root of the ezt-#.#.# dir. This will start the installer
-follow the installer instructions
-remove the install/ directory
Enhancements:
- cleaned up skin includes
- finished installer
- created basic readme
- cut initial release 0.01
- Implimented e-paging system
- got exporing to work (CSV)
- sticky/announce tickets working
- ticket escalations implimented
- Ported to arrays for selection queries, this allows multiple owners, priorities, etc to be selected
- Implimented "next page" links
- MANY other things
- cleaned up profile.php and added hooks for adding users
- added checks so regular users cant reopen tickets (only admins)
- added sticky ticket support (old PTR announce feature, but a little different)

The Bluetail Ticket Tracker (BTT) is a system for creating, storing and keeping track of tickets. A ticket describes an issue of some sort.

It can, for example, be a Trouble Report or a ToDo note. It is available for use (and distribution) under the GNU Public License.

The users of BTT are divided in four different user categories: Staff, Friend, Customer and Anonymous. The access to the data stored in BTT can be tailored for the Friend, Customer and Anonymous groups, while the Staff group has full access rights. This (hopefully) allows BTT to be used both for Open Source Projects as well as in more commercial settings.

In an Open Source Project:

* one or several people (Staff) hosts a site which runs the Ticket handling for a certain application
* a number of people (Staff + Friends) collaborates in the development which also include Ticket handling
* anyone else interested (Customer or Anonymous) may want to check the status of the Tickets (e.g Trouble Reports)

In a commercial setting:

* a company (Staff) runs the Ticket tracker as an aid in their product development.
* the company may be spread geographically or may have development partners (Friends)
* the customers can report problems and track the progression (Customer)

A ticket consists of a number of fields, e.g denoting a release name, component name, responsible person, staus, priority, etc. The actual field values is defined by the Staff when the Bluetail Ticket Tracker is setup. The daily operation of BTT includes creation, editing, searching and viewing of tickets.

The users can also activate the mail alert function which will send a mail to the user when, for example, a new ticket as been assigned to the user.

BTT can also store information about customers which can be useful in a support desk scenario. This makes it possible to connect a ticket with a particular customer. It is also helpful in a support desk scenario where the support engineer quickly need to find information about a customer.

BTT can also store more general information. This Knowledge Base consists of a mail store and a information store.

The mail store makes it possible to retrieve mails (from a POP3 account) and store it locally in a BTT directory. Stored mails can then be searched, viewed and turned into tickets.

The information store is divided in two parts, one external (for users/customers) and one internal (for staff/friends). The external area can for example be used for creating a FAQ (Frequently Asked Question), a HOWTO area. The internal knowledge base is intended for the Staff and/or Friends, and may for example store information such as address lists, how to fill in the expenses form, or contain description of the work process, etc.

Currently BTT supports English, French, German, Spanish and Galician. Adding new languages is easy, one language definition file has to be created with a translation of all text that can be displayed. (If you do this, make sure to send the new language file to the maintainers so that it can be incorporated into the standard release).

Tickets can also be retrieved and stored via a Unix command line interface.

Rubicon Tracker is a Ticket/Issue Tracking System written in C++ using an SQL backend to store and save all ticket information and history.
Tracker is a Web based system. All interaction occurs through a regular Web Browser. Tracker can be used for Bug Tracking, Phone/Help Desk Support, or any other process that requires tracking of items through phases.
Main features:
Issue Tracking from Majentis
- Rubicon Tracker is a Web based system for tracking and managing Defects and Issues in a project or muliple projects. Rubicon Tracker shares information among team members, clients, and management, offering an end-to-end Issue Managment solution.
Web Based
- Rubicon Trackers Web based format allows your team, clients, and management to collaborate from anywhere. Rubicon Tracker requires no Web Server to run, setup, or maintain. Rubicon Tracker is its own Web Server, geared specifically for this application, allowing speedy responses even under heavy loads.
Email Notification
- Keep all team members in the loop using instant notification by email when an issue (we call them tickets) is added or modified in any way. When a ticket is added, email is sent to all Project Managers registered with that project. Once the Project Manager decides who is best suited to work on a ticket, the person assigned is sent an email notifying them that they have a ticket. All modifications to the ticket will will generate email for all persona invlolved.
Move Tickets
- If a ticket is inadvertently added to the wrong project, a Project Manager can move the ticket to any other project the Project Manager has access to.
Online or Self-Hosted
- Majentis offers you two solutions for Issue Tracking. You can install and maintain Rubicon Tracker on your own servers, or you can use our on-line system, outsourcing your Issue Tracking needs.