Free to look software for linux

Quick Look is a package to collect system statistics and output pretty graphics and (X)HTML pages.
Quick Look allows system administrators to have a quick look on the status of their systems, without going for a more advanced (and heavier) solution.
Main features:
- CPU and memory usage
- Load average and process spawning rates
- I/O operations
- Network traffic rates
- Tracked network connections

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.

JavaInetLocator project is a Java library to look up the country code and language associated with an IP address.
It uses a local copy of the WHOIS database to perform fast, accurate lookups of country codes. It is useful for log analysis, internationalization, geolocation, and more.
Enhancements:
- The database was updated to February 2007.
- Locales were added for Aaland Islands (Swedish) (AX:sv), Jersey (English) (JE:en), Montenegro (Serbian) (ME:sr), and Serbia (Serbian) (RS:sr).

ost is a simple yet powerful tool providing mechanisms to automatically audit, maintain and backup systems customizations. ost is particularly well suited to environments where most systems are similarly configured, but will operate just as well if each system is unique.
ost uses at least one of the following two sets of input:
- the systems file catalog if it exists
- user defined "templates" to override the systems catalog
These allow ost to build a virtual image of what the local filesystem is supposed to look like. This image is then compared to the actual state of the local filesystem to obtain the following information about the system:
- List of intact files
- List of modified files
- List of missing files
- List of additional files

CookieSwap provides an extension that enables you to maintain numerous sets or profiles of cookies that you can quickly.
Main features:
- Changing your cookies/identity to web e-mail sites (like Yahoo, Gmail, Hotmail, etc) so that you can quickly look like different users. Nice if you maintain multiple accounts and are tired of logging out and then back in to switch accounts. Also nice if two people are using the same computer and want to switch between accounts quickly.
- Changing your cookies/identity to see how sites like Amazon and Google treat you differently depending on who you are. For example, if Amazon recognizes you as a returning shopper they give you a different looking page (and there were claims that they give you different prices also). Google has begun to use a feature called "Personalized Search", where they modify their search results based on your user identity. There is a question about this when you create your Google account. The results of Google searches are different depending on if Google knows you or not. Use CookieSwap to quickly swap between Google recognizing you and being anonymous. Run the same search and see the differences.
- If you design web sites, you can setup numerous cookie profiles to look like different types of users and swap between those users quickly and easily to test your site in numerous modes (you can hand edit the cookies to have distinct values in each profile using a nice extension like Add & Edit Cookies).

Linksys Syslog captures the snmp trap messages from a Linksys router and saves these to syslog. This daemon is very small robust and it does its job.

Ive gotten this router from a customer/partner DH computers to look at the VPN capabilities. Eventhough these broadband routers are small and cheap their VPN cabalities are okay. Its certainly not a Cisco PIX, but then again the Linksys costs 4 times less. The Linksys is very usable for the SOHO market and with no effort at all you can configure this device as a xDSL/Cable router.

After having looked at the specs I wanted to return this device to our customer/partner he told me that he gave it to me and if I didnt find a use for it that the company I worked for IT=it could keep it. So I decided to use this device because it has a 4 ports 100Mb/sec switch and I was still working on a 16 port hub at home.

After having updated the firmware to properly support MXSTREAM/PPTP I configured the router. But I wanted to setup logging for all in and outgoing traffic the way that I also had with my FreeBSD ipfw and ipf firewall. So I switched on Logging to my FreeBSD box. It struck me that I couldnt set the syslog facility and warning level, so it didnt seem like syslog. A quick snif with tcpdump revealed that the Linksys uses snmptrap to send the log requests. I used Ethereal to look in the packet to determine the layout of the snmptrap packet. The first 73 bytes are control data telling how large the payload, snmp version, etc. So I decided to only focus on the data from char 73 to the rest of the packet.

The program is very simple and straight forward. A UDP socket is opened and bound to port 162, the snmptrap port. The program goes in a loop and waits for data to be read; the programming works blocking. When data is in the read buffer the data is parsed by setting the string pointer to the 73 character. It is then being send to the syslog using syslog(), for the BSD version I used the SECURITY facility, for the non-BSD I use the DAEMON facility. The server is not multi client, which is not necesarry for this application. The handling is done so fast that theres no need for forking new processes or spawning threads. And since it is UDP we will not have to handle an accepts asynchronously to the actual client handler any way, data is being send and stored in the receive buffer by the IP stack.