Free trouble free 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

PHP TroubleTicket project is multiuser problem-tracking software entirely written in PHP 4.

It is designed to be used in a web-based client-server environment using the Apache webserver. A client can use just about any modern webbrowser and just about any operating system that is suitable for accessing WWW-Servers like any flavour of Microsoft Windows running the Internet Explorer, Netscape 6 and 7, Mozilla or Opera, Mac OS X or Unix/Linux/BSD systems with Netscape, Opera, Mozilla, KDE Konqueror, Gnome Galeon or Safari.

The dynamic webpages generated by PHP Trouble Ticket are designed to be widely compatible with most browsers and offer a concise and straightforward user interface.

RockBot is a fully functional multi-channel bot for IRC. It has hundreds of usefull commands for managing channels, amusing your friends, and protecting ownership. It is a good alternitive to an eggdrop type bot.
DCC model of rockbox is different like eggdrop. In RockBot YOU NEVER initiate a DCC chat with the bot. In all cases the bot will send you a DCC chat request when it needs one due to the type of data its returning. If you have trouble with DCCs it may be the bot cannotdetermine its true IP address on the machine. Try playing with "#define PPP" in config.h.
Enhancements:
- The data files and memory model were totally re-written. RockBot now uses a multiple-channel scheme for keeping track of users, and also allows one user to store multiple hostmasks under one "handle". There is also a "global" config that controls the default settings for channels and high level bot users. In order to diferentiate
- between global commands and local channel commands the following syntax has been implimented:
- (Note: This example assumes CMDCHAR is !)
- Sent to a channel -> !userlist = userlist of the channel typed in
- Sent to a channel -> !#mychannel userlist = userlist of #mychannel
- Sent to a channel -> !!userlist = global userlist
- ---
- Privmsg to bot -> #mychan userlist = userlist of #mychan
- Privmsg to bot -> !userlist = global userlist
- ---
- When you use JOIN a data file will be created to contain the new channels users, settings, topic etc. The LEAVE command parts the bot but does NOT remove the datafiles, however REMCHAN does.

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.

Pieces of Flare is an Eclipse Plugin which allows (J2EE) developers to synchronize source directories within their project to deployment directories on the AppServer.
Pieces of Flare plugin is written to allow automatic deployment of JSP files whenever they are saved, but it can be used for any file type.
Pieces of Flare only runs on files that are saved. With a custom ant builder you inflict the startup cost of ant within Eclipse, and Pieces of Flare knows what the changed deltas are - which a custom ant builder might not.
We were looking for a name that had something to do with Eclipse, and Flare came to mind. We were also talking about Office Space that day so it seemed like a decent choice.
Currently, the number one need is to develop some UI to do the XML configuration. If you would like to help out with that, contact one of the developers in the forums.
Enhancements:
- This version adds support for the scp file copy protocol for copying files to remotely located hosts.
- Also, there are improvements to the logging.
- It seemed that some people had trouble typing the fromDir and toDir paths.
- A simple check to see if these paths exist has been added.
- Hopefully this will make it easier to debug a configuration.
- Also, the debug attribute can be set to false to suppress info level logging once everything is working.

Free-SA is a statistic analyzer for Linux systems. Its main advantages over SARG are much better speed, more support for reports, and W3C compliance of generated HTML/CSS reports.
It can be used to help control traffic usage, to control Internet access security policies, to investigate security incidents, to evaluate server efficiency, and to detect troubles with configuration.
Enhancements:
- Better support for different Postfix log files (still experimental, but closer to stable).
- There are also some cross-platform fixes and code improvements.
- New file extensions have been added for the downloads report.

Microdrive is basically a set of scripts which you can use to make your own live linux cd.
It depends on busybox, isolinux and linux of course.
I am planning to build a small bunch of diskless, monitorless, keyboardless nodes to do my rendering work [3D]. For them to run, I have various options but live cd seem to be most trouble free.
But then I couldnt find a live cd, that more or less faithfully follows a ordinary installed linux system. They seem to use squashfs or unionfs or some other form of pseudo writable file systems. I couldnt even get the slax to show me a screen. I am sure it is to do with my laptop graphics card.
But it sort of inspired me to make my own live cd, so I can match the components to the same library versions of my installed systems.
To this end instead of making a single cd, I broke the work needed in to a set of scripts so that the whole thing is manageable and reusable.
Hopefully it will be useful to someone else out there.
To make a live cd :
1. Get the Microdrive Linux Live script set from above.
2. Untar the files to a directory.
3. Make a kernel appropriate for live cd.
needs initrd, ramdisk and ext2
preferably also support basic devices as below. [ cd, devfs, framebuffer, vesa etc ]
No hard and fast rules. Afterall its your damn cd!
4. Copy the kernel to ./src/bzImage .
5. Download busybox source tarball and put it in ./src .
6. Download syslinux source tarball and put it in ./src .
7. Run the scripts listed in ./scripts directory. [ Please note. Dont cd in to scripts directory. Rather run them as ./scripts/SCRIPT_NAME . All the scripts assume that they are working from directory where ./src and ./scripts ./doc etc are the sub directories.]
8. The purpose of scripts [ At first run them in this order as well ] :
./scripts/make-prelim-dirs : This will make all the necessary directories such as itree - where the initrd image will be made. cdtree - whatever is here will endup on cd. cdtree/zz - whatever other software you want to install, install it here. Also /etc/rc.d/links on the live cd will link lib, usr, etc, etc/X11/* from here to the live system during runtime. cdtree/isolinux - where the initrd.img, isolinux end up.
./scripts/build-busybox : This will build and install busybox in to itree. Will also chmod u+s the busybox library.
./scripts/build-isolinux : Well, guess what.
./scripts/find-libs : After installing the busybox binaries, you will ofcourse need the libraries i:e; libc, libm, ld-so etc. Well, this does exactly that. It cannibalises them from your host system.
./scripts/install-base : This will install a basic /itree/etc to go in to initrd.img. You can customize the actions there to your hearts content.
./scripts/update-itree : As root, this will ldconfig the libs in itree. Then chroots to the itree. You should get a shell. If it doesnt work here, it aint gonna work on the cd.
./scripts/make-initrd : You need to run this as root. Please read the script before reaching out for the "su" . It will create a initrd.img from itree/ and puts it in cdtree/isolinux/ . This is what the kernel from live cd loads and feels content that it has a root file system.
./scripts/make-iso : Finally ! . Make a iso9660 bootable image to burn to cd or cdrw.
9. In other words :
./scripts/make-prelim-dirs
./scripts/build-busybox
./scripts/build-isolinux
./scripts/find-libs
./scripts/install-base
./scripts/update-itree [ as root ]
./scripts/make-initrd [ as root ]
./scripts/make-iso
Enhancements:
- Updated for the new kernel.
- No devfs now.

NetEclipse is a suite of tools created for testing TCP/IP weaknesses and using them in a non-conventional way, such as testing security and limits of IP version 4 protocols.
The Makefile is extremely simple but it should do its work... To install extract the package "neteclipse-x.xx" and launch "make".
If you got into trouble:
first check if you have LibPcap installed and if the version isnt too old.Try to install the version included in the package (read the INSTALL file in /libpcap-0.7.1/ before!!) and then, if it doesnt work yet, launch "make report" and send me the make_errors.log file at
Enhancements:
- Version 2.0 of the manual
- Minor changes in the code