Free tracker software for linux

Tracker is a first class object database, extensible tag/metadata database, search tool and indexer.
It can trawl through your hard drive and index existing files and data stores.
It has been designed from the ground up to be very lightweight (the tracker daemon consumes ~4MB of RAM in typical use) yet at the same time very fast too.
It provides a comprehensive, persistent and extensible storage system that can store and index almost any object. These objects can also have extensible user defined metadata and tags to create rich first class objects.
First class object support includes:
- Files
- Documents
- Music
- Images
- Videos
- Text Files
- Development Files
- Playlists*
- Notes*
- Applications*
- People/Contacts*
- Emails*
- Conversations*
- Appointments*
- Tasks*
- Bookmarks and History*
- Projects*
(* these services are not currently indexed at the moment but will be in later versions)
Main features:
- Desktop-neutral design (its a freedesktop product built around other freedesktop technologies like DBus and XDGMime but contains no GNOME specific dependencies)
- Very memory efficient and non-leaking (typical RAM usage 4 - 6 MB). Unlike some other indexers, tracker is designed and built to run well on lower memory systems with typically 128MB or 256MB memory. It should even be efficient enough to use on some mobile devices.
- Non-bloated and written in C for maximum efficiency.
- Small size and minimal dependencies makes it easy to bundle into various distros including live cds.
- Fast indexing and unobtrusive - no need to index stuff overnight. Tracker runs at nice+10 so it should have a minimal impact on your system.
- Implements the freedesktop specification for metadata http://freedesktop.org/wiki/Standards/shared-filemetadata-spec
- Extracts embedded File, Image, Document and Audio type metadata from files.
- Extracts embedded metadata from HTML, PDF, PS, OLE2 (DOC, XLS, PPT), OpenOffice (sxw), StarOffice (sdw), DVI, MAN, MP3 (ID3v1 and ID3v2), OGG, WAV, EXIV2, JPEG, GIF, PNG, TIFF, DEB, RPM, TAR(.GZ), ZIP, ELF, REAL, RIFF (AVI), MPEG, QT and ASF files
- Supports the WC3s RDF Query syntax for querying metadata
- Provides support for both free text search (like Beagle/Google) as well as structured searches using RDF Query
- Respond in real time to file system changes to keep its metadata database up to date and in synch
- Fully extendable with custom metadata - you can store, retrieve, register and search via RDF Query all your own custom metadata
- Can extract a files contents as plain text and index them
- Provides text filters for PDF, MS Office, OpenOffice (all versions), HTML and PS files.
- Can provide thumbnailing on the fly

Diet Tracker is a set of Perl codes to help you keep track of your diet progress. Diet Tracker uses a MySQl database to store and display your weight variations and calorie intake as you progress in your diet.
This software was inspired by Jeremy Zawodnys Excel spreadsheet that does almost the same thing. I wanted a web version that was simple and meant for single user and not finding any, wrote one.
Main features:
- Web based
- Track calorie intake per day
- Graphs to track weight and intake history
- Moving average calculation to even out jitters
- Automatic BMI calculation
- Clean interface

GPS Tracker project allows someone to track a GPS enabled cell phone using Google maps. For this project I used a Motorola i355 cell phone on the Sprint/Nextel network.
You need to have a data plan so that you can make updates to your website from the cellphone. Please read the ReadMe.txt file in the download for installation instructions. I hope you enjoy the project. If you have any questions, feel free ask them in the forum.
There are two projects available. The first project is built with .NET and Microsoft SQL Server. The second project is built with PHP and MySQL. If you have any suggestions, please feel free to let me know. Both projects use java (J2ME) on the phone.
How It Works:
None of the code for this project is very difficult, but it does span a number of tiers and languages which may be unfamiliar to some. Figure 1 shows the data flow from phone to Google map.
Phone
Lets start with the code on the phone. This app is written in java using Java 2 Micro Edition (J2ME). Java is very similar to C#. As you look through the code, the only thing that might confuse a C# coder is the vector. A java vector is pretty much a C# ArrayList, a dynamic array. There are 2 classes in the app, LBSMidlet7 and Qworker. A midlet is an app that runs on cell phones. Take a look at the class definition. It extends the MIDlet class and implements a LocationListener interface. That means that we need to put all the method definitions of that interface into our class. Well get to that in a bit, right now lets look at the constructor.
We do 2 things in the constructor. We create a QWorker object and pass it "this" and the website that we will be uploading to. The getAppProperty method gets attributes out of the JAD file. Open the JAD file in your favorite text editor and there youll see the webpage that youll be sending GPS data to. Notice how were passing "this" to the GWorker object? Thats the LBSMidlet7 object. Take a quick look at the QWorker class, it extends the Thread class. Thats why we call worker.start() in the LBSMidlet7 constructor. We want to start our worker thread.
When you start a thread, what you are doing is creating an object and then running that objects run() method. Take a look at the run method. It has an endless loop and in the loop the first thing it does is call queue.wait(). Look at the definition of the queue. The queue is an abstract data type (ADT), it just like a queue at a bank, enter the queue at the back of the line and leave the queue when you get to the front of the line. Look at the definition of the queue, its our vector (dynamic array). When you call wait() on an object within a class that extends the Thread class, it puts that object to sleep. Think about that a little. When we hit that line, our QWorker object is now waiting... Whats it waiting for? Well get to that in a minute. Before we do that, take a look at the synchronized keyword. Notice that its wrapping the queue. What that does is it puts a lock on the queue and tells all other processes not to touch the queue until that little block of code is done with it.
Ok, so now weve started a worker thread and put it to sleep. Lets now go back to the LBSMidlet7 class and take a look at the startApp() method. In the lifecycle of a midlet, the constructor is called once and then the startApp() method is called next. In fact it can be called several times, like for instance when you close a flip phone and then open it again. What happens is that the app is suspended and when you flip the phone open again, startApp() is called again. In startApp(), we get our display and then we create a LocationProvider if one hasnt already been created and we create another thread... Why are we creating all these threads? Good question. When a midlet (app) is suspended, the backgroud threads that are created keep running. That allows us to get our GPS data and send it to our webserver while we do other important stuff, like make phone calls.
The LocationProvider is what gets our GPS data. First we create a criteria, were using the default, but you can set stuff like accuracy, response time etc. Next we create our Location Listener. Its pretty much just what it sounds like. Here you can set the interval for how often you want to get GPS data. Its currently set to 60 which is in seconds. When data comes in, the locationUpdated() method is called. This is another one of the required methods in the LocationListener interface. Here we create yet another thread and call getLocation(). The getLocation() method gets the GPS coordinates, creates a queryString which we will send to the web server a little later and then calls worker.addToQueue in the QWorker class.
Lets go back over to the QWorker class and see what happens in that method. It add the queryString to the queue and then calls queue.notify(). Guess what queue.notify() does? It wakes up our sleeping QWorker thread and tells it to get to work! Notice that our calls to the queue are once again wrapped in a synchronized block. Please practice safe threading... When notify() is called on a thread, what it does is go back to the run() method and execute the next line of code right after where we told the queue to wait(). So now we are just about ready to send the GPS data to the web server. We have a couple of interesting lines of code there. First we call peekInQueue() which gets the queryString out of the queue but leaves it there for now. Then it sends the queryString to the getUrl method which attempts to send the queryString to our web server. If its successful, we can remove the queryString from the queue. If not, we leave the queryString in the queue and try to send it to the webserver again later.
Why in the world do we have this complicated queue here? Im glad you asked. There may be times when you are receiving GPS data but are not actually in an area that has a cell phone connection. If we dont have a cell phone connection, we cant send our GPS data to our web server. So we stick our queryString in our queue and wait until we get back into an area with cell phone connectability. Can you hear me now?
Well, weve spent a pretty fair bit of time explaining the phone code. Its a little complicated but its important to know whats going on if you want to take the code and make modifications to it to suit your needs. Heres a good article on the Sun website to let you know about more capabilities of the Location Based Services API. Right about now, our queryString should be arriving at our website, lets catch up to it and see what happens.
Enhancements:
- Added comments to code

TimeTracker is an application loosely based on TimeKeeper, a Windows application used to track the time you spent on a task.

Being a Linux user and not willing to install Wine, I decided to hack my own version.

Digg Tracker is an extension provided by Netscape which allows you to keep tabs on what stories you and your friends are diggin.

Netscapes Digg Tracker extension helps you keep tabs on what stories your Digg friends are digging, submitting, and commenting on. A new toolbar button (shown in the preview image) features the Digg digger. When there is new activity by your friends (i.e., a new comment or a new story submission), the button will be activated and the digger will be shown with his trusty shovel.

Clicking on the activated button will open a list of your friends activity in the sidebar, allowing you to easily browse the stories theyve submitted, commented on, and dugg. Each time you view your friends activity, you will only be shown activity that is new since the last time you opened the sidebar.

In addition, the top 5 stories from Netscape.com will be shown below your friends activity. At any time, you can click the toolbar button to view these links, even if there is no new activity to display.

Network Tracker application is a user (MAC) tracker daemon, for big LANs (campus).
The Network Trackerd builds a table which records which user is connected on which port of a switch by scanning the devices with SNMP in your inventory which is in a MySQL database. Trackerd keeps that table up-to-date by scanning the network regularly.
Thus, you will have the opportunity to know exactly where a user (MAC, IP, UID) is connected on your network !
Your devices are also checked with ping and SNMP, and you are informed with e-mail when any of the devices is not alive.
More over, you may produce various reports about your network infrastructure on the web (cgi) or by using other tools.
Network tracker eases especially to find and shutdown the switch port of the users, when their PCs on the network start to spread viruses or warms using lots of bandwith; so you are able to stop that kind harmfull traffic on the network.
Main features:
- Collects all the MAC addresses and port numbers from CAM tables of the switches.
- Finds IP addresses of the MACs from ARP tables of the routers.
- Finds LDAP uid of the user.
- Check devices on the network with both ping and SNMP for better reliability.
- The daemon sends 2 self check e-mail per day.
- Developped with C.
Enhancements:
- trackerd is now multi-threaded and works very quickly because a new thread is created for each network device.
- MAC tracking code has been reimplemented for multi-threaded use.
- Wireless access point support has been added.
- gnuplot graphics are prepared, showing the active number of users like MRTG graphs.
- tracker now accepts MAC addresses in free format.

Shake tracker is a MIDI sequencer aimed to all the tracker lovers who allways wanted to go midi, while keeping all sort of cool tracker features.

Shake tracker has a tracker-like interface which supports patterns, orders and IT-like effects.

Each track (midi channel) is subdivided in columns of its on, so this adds an extra layer to pattern editing. Note on, Noteoff and velocity are also implemented the usual way, while the effect column understands most of IT commands with similar parameter ranges. Finally, theres also a controller/effects column and plans for adding "paintable controllers" support.

Shake tracker has been programmed with MIDI bandwith issues in mind, so its perfectly usable on external synths, softsynths and soundcard synths. There is actually a Windows version of this program, but its not native and it needs you to install an Xserver.

Many features of modern sequencers are still missing, such as sysex and midi in, but the program is perfectly usable and many people wrote songs with it (check downloads section).