Last night I ran a quick test on how long my new Dell Inspiron Mini 9’s battery would last under “normal netbook workload”.
Details:
- OS: Gentoo Linux (what else?
)
- Running programs: KDE 4, Konqueror, Thunderbird (fetching mail via IMAPS every 5 minutes)
- Conditions:
- Wireless connection to Internet, shell script kills and reloads Konqueror with three websites every two minutes (emulating a user who browses the WWW).
- Display set to lowest brightness level, screensaver / standby / etc. deactivated so that it was switched on all the time
Data capturing:
The ‘remaining capacity’ value from /proc/acpi/battery/BAT1/state and a timestamp were written to a file every minute:
#!/bin/bash
LOG="/home/pn/batterylog"
echo "Battery log, started $(date)" >$LOG
while ((1))
do
TIME=$(date "+%s")
REMAINING=$(grep "remaining capacity" /proc/acpi/battery/BAT1/state | cut -b 26- | cut -d' ' -f1)
echo "$TIME $REMAINING" >> $LOG
sync
sleep 60
done
Results:
The battery lasted a little longer than 4 hours and 50 minutes which means approx. 6.7 watts average power consumption while browsing the web over WLAN.
This time I decided to use OpenOffice Calc to create the graph - here is a screenshot of it:
(And here is the spreadsheet, if you’re interested: Dell Mini battery consumption log (Spreadsheet))
Today I was trying to upload a lot of mail (something like 160000 mails stored in a deeply nested folder structure of about 13000 folders) to an IMAP server. Those mails were converted from the Eudora mailbox format to a more sane Eudora mailbox format using “Eudora rescue”, and then imported into Thunderbird’s “Local folders”. From there, so we thought, it would only be a matter of minutes to put those mails onto the newly setup dovecot IMAP server, with one drag-and-drop action.
But…
The upload horribly failed after the 3rd folder or so, with no error message whatsoever. No matter what I tried, it would just fail silently. The debug logging (see Debugging/Thunderbird article in the Dovecot wiki) didn’t help, and neither did dovecot’s log on the server. The problem seems to be connected with creating folders on the server somehow - because uploading a big amount (400 for a small test) mails within one folder wasn’t a problem. I couldn’t find out if Thunderbird or dovecot is to blame here…
I eventually managed to get this big pile of mail to the server by using a perl script that I found on perlmonks.org. Thanks to Davis for providing this! I downloaded it, installed the Mail::MboxParser and Mail::IMAPClient dependencies (with two ‘cpan install …’ calls), changed the configuration in the script to our site’s data and ran it. ~30 minutes later, the mails were on the server. Only thing that could have been better: All mails were ‘marked as unread’ - but that’s easy to fix.
Update:
After looking into the perl code, I found a way to ‘mark as read’ during the transfer. I posted it under the original perlmonks.org script as a comment.
I’m using this setup for quite a while now. It’s great in many ways - here some of the reasons:
- I can access it from multiple hosts at once
- I can use one unified user interface for all instant messenger protocols and IRC
- I can access the platform even through my mobile phone via GPRS / WLAN
- I have logs of all communications in one central place
This is how a few free software components work together to make it possible:
Overview (OpenDocument format)
Or as PNG file (rendered with GIMP):
