What is SETILog for Unix?

SETILog for Unix is a port of the Windows program SETILog written by Mark Loukko. It is designed to be run after your SETI@home client has completed a work unit. SETILog then extracts and stores some information about the workunit in a seperate file.

February 14, 2004: Version 1.4.4 Released

Thanks for some excellent feedback and ideas (mostly from Steve Wilson) I have just release version 1.4.4 of SETILog. This version is mainly focused on big fixed and contains no new features. If you are not experiencing any problems, there is no need to install the update.

May 20, 2003: verison 1.4.2 Released.

Some minor bug fixes and the addition of the stop_after_send.txt file. Binaries will show up on the SourceForge project page over the next couple of days as I get them built.

September 2, 2002: SETILog version 1.4.0 Released

A couple of minor enhancements over SETILog 1.3.0. Support the -k command line option to kill a runnin daemon Ability to pass command line options to the SETI@Home client Binaries will show up on the SourceForge project page over the next couple of days as I get them built.

June 24, 2002: SETILog version 1.3.0 Released

Wow, after about 6 months, I finally collected (and implemented) enough bug fixes and new features to justify a new version. Over the next couple of days I will be building and uploading binaries to the SourceForge project page.. Here is a brief run down of the new features Support for daemon mode operation. Bug fixes (including removal of all know memory leaks). Support for more of the fields used by the 3.0 version of SETI@Home. Log file compatibility with SETIWatch

October 2, 2001: Solaris, AIX and HP-UX builds added

I have built and packaged binaries for Solaris (2.6+), AIX (4.3+) and HP-UX (11.00+) and added them to the project page.

September 28, 2001: Version 1.1.0 Released on SourceForge

Well, well, well. Looks like I have aquired myself a project. I had been using Tobias Meyer's SETILog for several months to log the results of my SETI@home work units on various Linux boxes I have floating around. Then I decided that I wanted a copy for OpenBSD. I emailed Tobias and discoved that he did not have the time to provide or maintain an OpenBSD port. Then he generously suggested that if I wanted, he would turn the project over to me to maintain. So SETILog for Unix has a new maintainer, and a new home. I chose SourceForge.net to host the code and binaries and uploaded builds of the current code for Linux and OpenBSD. There have been no code changes in this version, so if you found a bug with a previous version, don't bother to upgrade to 1.1.0, this is just a rebranding. Email me or log a bug and it should be fixed in the next version. No, I don't have a date for that yet. If there is any demand for it, I will do it.

What Can I Do with It?

Once you have the data from you completed work units, there are a couple of things you can do. You can import the log file directly into your favorite spreadsheet and play with it there. or you can use the SETIWatch program which can read the log files directly. I use this program myself and highly recommend it. The Cool Factor is pretty high.

Help, Bugs, Feature Requests

I am actively encouraging and soliciting feedback and bug reports for SETILog. If you have a suggestion, comment, bug report, complaint or just want to make some noice, I want to hear from you. Check the contact page to find out how to get in touch with me.

Who are You?

My name is Robert Clark. I am a software developer living in Toronto, Canada. You can reach me at setilog@exiter.com. However, since I run my own mailserver, I have installed some draconian spam filters. If your email gets rejected, you can either:

• Resend it to postmaster@exiter.com and I will check to see if I can unblock your address.
• Log a bug or support request on the SourceForge project page.

The PGP key I use to sign the RPM packages of SETILog is available here and has the KEY ID 0x0E9903E1. I used this key to sign allmy email. The KEY ID for it is 0xB13B653B. Both keys should be listed in the public database at http://www.pgp.net/wwwkeys.html.