Focus-follows-mouse coupled with the disabled Raise-on-focus window property is a mode of operation for a window manager, highly targeted at the professional use, unheard of in the Microsoft Windows world. Yet, it takes some fine configuration tweaks to get it to the prime-time. Read More
SPF (Sender Policy Framework) is cool stuff and when implemented properly helps vanity domain owners play on par with big email service providers, like gmail.
However, in its basic form it presents privacy concerns for small offices operating out of their homes, or any other small mail senders.
The problem is that anyone on the Internet can look up a list of IP addresses allowed to send mail for a given domain. Some users may feel uneasy having their home IP address known to everybody.
Here is how this issue can be resolved while still reaping full benefits of SPF.
Right after I got my quite elaborate Nagios setup running in my local network, I thought to myself “What if my network loses connectivity to the world and my GSM-SMS gateway fails? How am I going to be notified of such a grand disaster?”
Well, as usual, a shell one-liner comes to rescue.
DreamHost changed SSL cert for mail once again.
- Put CA certificates in
/usr/local/share/ca-certificates/, and NOT the system directory /usr/share/ca-certificates/
- run update-ca-certificates to update the compiled list of CA certificates.
- Add the path to /etc/postfix/main.cf :
smtp_tls_CApath = /etc/ssl/certs
… but I was too lazy to pursue that way to the end, so I ended up just updating the fingerprint for use by the postfix SMTP client.
Steps to add (update) fingerprint checking to Postfix SMTP client:
The tar’s “–exclude=PATTERN” option has always had me perplexed. As this is mostly intended for automation scenarios, I have never paid much attention to this option resorting to its more “pro-batch” variant “–exclude-from FILE”.
But today, as I went about making some backups I thought it’s enough, I need to learn how to use this option effectively. Having realized that the documentation on the matter is quite lacking, I decided to make a simple experiment.
Here are the commands I typed (in a bash terminal) to learn more about the “–exclude=PATTERN” option:
Use the following one-line script to control witch EXIF data to leave in the photos published online:
exiftool -P -overwrite_original -all= -tagsFromFile @ -ExposureTime -MeteringMode -Flash -FocalLength -FocalLengthIn35mmFormat -FocusDistance -VibrationReduction -FocusMode -CreateDate -DateTimeOriginal -ISO -FNumber -UserComment -copyright='(c)2011, Alexander Shcheblikin' -artist='Alexander Shcheblikin' -model="Sasha's DX dSLR" _DSC*jpg
This should all be entered on one line (note: the dashes which hang over the ends of the lines must actually be adjacent to the command line switches following them).
This is a power tool affecting multiple files at once and it will process all the files matching _DSC*jpg pattern in the current directory.
To retain original files remove the
exiftool is available natively in Linux/UNIX as a Perl library and a front-end script and as a standalone executable for Windows and a package for Mac OS X.
WordPress is so good for SEO in part thanks to the large number of data fields available for each post: post title, excerpt, name (slug) and, finally, content. This allows for deep customization when presenting your post to the WWW.
While it’s fine to fill all those fields for a regular article it may be an overkill for a picture for that same article (which is just a sub-post in terms of WordPress built-in media library). (And even for a normal article – how many of us really do enter post excerpts? Yes, that’s what I’m talking about.)
I usually record movies off TV with only one soundtrack – English. And it happened that I needed to give one such movie to someone Russian-speaking.
The solution was to find the appropriate subtitles in Russian and hand the subtitles file along with the video file.
The only problem was the subtitles were for the DVD version of the movie and I only had a TV recording.
A little Perl programming effort did the trick.
In your web-stats, you may sometimes find an unknown referrer, which might have sent you a few visitors. Intrigued by it you go and grep Apache’s access.log to see what those visitors came to read:
grep "referrer" access.log | less
That line is enough in most situations, but what if you get intrigued yet further and want to know if these visitors stayed for anything more at your site?