|October 8th, 2011|
|tech, startups, logging, ideas [html]|
When writing a friend to ask what they thought, however, I did some additional searches, and this time found that someone already made this. And they have many competitors. It also turns out not to have been all that good an idea: none of these companies seem to be doing all that well. So I should actually be happy that someone else already tried this: finding out it was not a good idea in two days is much better than in a year.
I'm still running the code, because I might find the data useful some day, and if you're interested in it, I put it on github. It's mac only, and not ready for non-programmers to use, but the usage information is:
Compilation: $ gcc -o prodlog log.m -framework Foundation -framework AppKit -framework IOKit -Wall Installation: $ sudo mv prodlog prodlog_helper.sh /usr/local/bin/ Testing: $ prodlog 1318078591 0 Terminal # format is epoch timestamp, seconds idle, active app name Run automatically: $ crontab -e * * * * * /usr/local/bin/prodlog_helper.sh Observe: $ ls ~/.prodlog/ 131800.log.gz # past files are gzip compressed 131801.log.gz 131802.log.gz 131803.log.gz 131804.log.gz 131807.log # current file is not compressed lock $ zless ~/.prodlog/131802.log.gz | tail -n 4 1318029688 0 Google Chrome 1318029689 1 Google Chrome 1318029690 2 loginwindow 1318029691 3 loginwindow Each file should hold up to 10k samples and represent about three hours. In a year you should use about 30MB. licensing --------- idler.h - see copyright notice in the file log.m, prodlog_helper.sh - I release these into the public domain