Free cheap round trip airline tickets software for linux

PHP Trouble Ticket project provides a centralized means of problem reporting and tracking in multi-user environments (medium to large companies, development groups, etc.).
It helps direct problem reports to the responsible administrator(s), keeps track of the status of a problem being worked on, and offers an up-to-date list of recent changes applied. It aims to be widely configurable, easy-to-use even for those not technically inclined, and multi-language capable.
Main features:
- problem reporting
- submitting update-info
- email-notification of administrators
- email-notification sent to problem reporter after ticket is modified or closed
- watch-function for tickets to be kept up to date on progress of chosen tickets
- file attachments (including on-the-fly virus checking with external virus-scanner)
- powerful list/search function with paged browsing
- tickets can be set into relations/dependencies
- ticket quick-search function directly from the main index
- quickly access all your own tickets from the main index page
- printer-friendly display of lists and ticket details
- css style sheet support for easy customisation
- easy multiple-select/close/delete functions
- username/password protected logins
- varying levels of permissions/access-rights
- the scope of unprivileged users can be limited to their own tickets
- new users can either sign up at the login page or be created by the superuser from the administration page
- detailed userlist available for administrators with info on last login and included search function
- online configuration of all major options
- configuration of the expert/administrator information
- deadlines for trouble tickets
- up to five customizable datafields
- changes and entire tickets can be hidden from unprivileged users by the operators
- "locking" areas against change by other administrators
- national language support (included: english, german. Other language files are made available separately on the download page)
- date/Time format configurable to suit national format
- ability of the program to work with PHPs "safe mode" and "open basedir" security mechanisms

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.

Trip on the Funny Boat is a side scrolling shooter game starring a steamboat on the sea.

Trip on the Funny Boat is side scrolling arcade shooter game on a steamboat equipped with a cannon and the ability to jump. The player will need to take advantage of waves to defeat the enemies and dodge hazards.

This game was made for the second PyWeek competition during the week from 25.3.2006 to 2.4.2006.

The Wonder Shaper is a very special network shaper script with a lot of features. Works on Linux 2.4 & higher.

Goals

I attempted to create the holy grail:

* Maintain low latency for interfactive traffic at all times.

This means that downloading or uploading files should not disturb SSH or even telnet. These are the most important things, even 200ms latency is sluggish to work over.

* Allow surfing at reasonable speeds while up or downloading

Even though http is bulk traffic, other traffic should not drown it out too much.

* Make sure uploads dont harm downloads, and the other way around

This is a much observed phenomenon where upstream traffic simply destroys download speed. It turns out that all this is possible, at the cost of a tiny bit of bandwidth. The reason that uploads, downloads and ssh hurt eachother is the presence of large queues in many domestic access devices like cable or DSL modems.

Why it doesnt work well by default

ISPs know that they are benchmarked solely on how fast people can download. Besides available bandwidth, download speed is influenced heavily by packet loss, which seriously hampers TCP/IP performance. Large queues can help prevent packetloss, and speed up downloads. So ISPs configure large queues.

These large queues however damage interactivity. A keystroke must first travel the upstream queue, which may be seconds (!) long and go to your remote host. It is then displayed, which leads to a packet coming back, which must then traverse the downstream queue, located at your ISP, before it appears on your screen.

This HOWTO teaches you how to mangle and process the queue in many ways, but sadly, not all queues are accessible to us. The queue over at the ISP is completely off-limits, whereas the upstream queue probably lives inside your cable modem or DSL device. You may or may not be able to configure it. Most probably not.

So, what next? As we cant control either of those queues, they must be eliminated, and moved to your Linux router. Luckily this is possible.

Limit upload speed somewhat

By limiting our upload speed to slightly less than the truly available rate, no queues are built up in our modem. The queue is now moved to Linux.

Limit download speed

This is slightly trickier as we cant really influence how fast the internet ships us data. We can however drop packets that are coming in too fast, which causes TCP/IP to slow down to just the rate we want. Because we dont want to drop traffic unnecessarily, we configure a burst size we allow at higher speed.

Now, once we have done this, we have eliminated the downstream queue totally (except for short bursts), and gain the ability to manage the upstream queue with all the power Linux offers.

Let interactive traffic skip the queue

What remains to be done is to make sure interactive traffic jumps to the front of the upstream queue. To make sure that uploads dont hurt downloads, we also move ACK packets to the front of the queue. This is what normally causes the huge slowdown observed when generating bulk traffic both ways. The ACKnowledgements for downstream traffic must compete with upstream traffic, and get delayed in the process.

We also move other small packets to the front of the queue - this helps operating systems which do not set TOS bits, like everything from Microsoft.

Allow the user to specify low priority traffic (new in 1.1!)

Sometimes you may notice low priority OUTGOING traffic slowing down important traffic. In that case, the following options may help you:

NOPRIOHOSTSRC
Set this to hosts or netmasks in your network that should have low priority

NOPRIOHOSTDST
Set this to hosts or netmasks on the internet that should have low priority

NOPRIOPORTSRC
Set this to source ports that should have low priority. If you have an unimportant webserver on your traffic, set this to 80

NOPRIOPORTDST
Set this to destination ports that should have low priority.

See the start of wshaper and wshaper.htb

Results

If we do all this we get the following measurements using an excellent ADSL connection from xs4all in the Netherlands:

Baseline latency:
round-trip min/avg/max = 14.4/17.1/21.7 ms

Without traffic conditioner, while downloading:
round-trip min/avg/max = 560.9/573.6/586.4 ms

Without traffic conditioner, while uploading:
round-trip min/avg/max = 2041.4/2332.1/2427.6 ms

With conditioner, during 220kbit/s upload:
round-trip min/avg/max = 15.7/51.8/79.9 ms

With conditioner, during 850kbit/s download:
round-trip min/avg/max = 20.4/46.9/74.0 ms

When uploading, downloads proceed at ~80% of the available speed. Uploads at around 90%. Latency then jumps to 850 ms, still figuring out why.

What you can expect from this script depends a lot on your actual uplink speed. When uploading at full speed, there will always be a single packet ahead of your keystroke. That is the lower limit to the latency you can achieve - divide your MTU by your upstream speed to calculate. Typical values will be somewhat higher than that. Lower your MTU for better effects!

A small table:

Uplink speed | Expected latency due to upload
--------------------------------------------------
32 | 234ms
64 | 117ms
128 | 58ms
256 | 29ms

So to calculate your effective latency, take a baseline measurement (ping on an unloaded link), and look up the number in the table, and add it. That is about the best you can expect. This number comes from a calculation that assumes that your upstream keystroke will have at most half a full sized packet ahead of it.

This boils down to:

mtu * 0.5 * 10
-------------- + baseline_latency
kbit

The factor 10 is not quite correct but works well in practice.

Your kernel

If you run a recent distribution, everything should be ok. You need 2.4 with QoS options turned on.

If you compile your own kernel, it must have some options enabled. Most notably, in the Networking Options menu, QoS and/or Fair Queueing, turn at least CBQ, PRIO, SFQ, Ingress, Traffic Policing, QoS support, Rate Estimator, QoS classifier, U32 classifier, fwmark classifier.

In practice, I (and most distributions) just turn on everything.

The scripts

The script comes in two versions, one which works on standard kernels and is implemented using CBQ. The other one uses the excellent HTB qdisc which is not in the default kernel. The CBQ version is more tested than the HTB one!

See wshaper and wshaper.htb.

Tuning

These scripts need to know the real rate of your ISP connection. This is hard to determine upfront as different ISPs use different kinds of bits it appears. People report success using the following technique:

Estimate both your upstream and downstream at half the rate your ISP specifies. Now verify if the script is functioning - check interactivity while uploading and while downloading. This should deliver the latency as calculated above. If not, check if the script executed without errors.

Now slowly increase the upstream & downstream numbers in the script until the latency comes back. This way you can find optimum values for your connection. If you are happy, please report to me so I can make a list of numbers that work well. Please let me know which ISP you use and the name of your subscription, and its reputed specifications, so I can list you here and save others the trouble.

Installation

If you dial in, you can copy the script to /etc/ppp/ip-up.d and it will be run at each connect.

If you want to remove the shaper from an interface, run wshaper stop. To see status information, run wshaper status.

KNOWN PROBLEMS

If you get errors, add an -x to the first line, as follows:

#!/bin/bash -x

And retry. This will show you which line gives an error. Before contacting me, make sure that you are running a recent version of iproute!

Recent versions can be found at your Linux distributor, or if you prefer compiling, here:
ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz

easy TicketManager project is a system for managing customer requests (trouble tickets or similar) for a group of users.
Each ticket is assigned to a customer and a carer who is responsible for handling this ticket. Tickets can be organized in folders or by categories and can have notes attached to them.
Enhancements:
- You can manage tickets and define a workflow to handle these items.
- The installer has been improved, as well as the plugin concept.
- The following plugins are shipped and installed automatically: notes management, bookmarks management, and the ticket plugin.