$ ssh -n MAILSERVER tail -1000f var/log/procmail-from | ~/bin/procmail-from2diary.pl
Blog
-
a more readable procmail log file – formatted as emacs style diary – this is how I watch my incoming mail
-
camera pictures and their file names, PDF files – if you want them to carry some date they already have inside their header …
- https://github.com/JochenHayek/misc/blob/master/jpg-exif-suggest-rename-as_vouchers.sh
- https://github.com/JochenHayek/misc/blob/master/jpg-exif-suggest-rename-versioned.sh
- https://github.com/JochenHayek/misc/blob/master/pdf-suggest-rename-as_vouchers.sh
- https://github.com/JochenHayek/misc/blob/master/pdf-suggest-rename-versioned.sh
For accessing the EXIF header there are a couple of utilities available, “exif –xml-ouptut” and “exiftool -s”; for PDF the package “xpdf” provides a utility called “pdfinfo -meta -rawdates”. All of them can provide you with quite a few date-time-strings from the respective heards.
Long ago I wrapped these utilities in nice little shell scripts, that take all these date-time-strings and list the possible renaming commands with descriptive comments (“mv … … # …”) on STDOUT, so that you can pick from the alternatives.
One variant of my wrapper scripts suggests renamings, that put the date-time-string at the beginning of your file name, so that your files will get sorted by the date and time, that they got created on – that’s usually, what I pick.
The other variant puts the date-time-string right before the extension of the file.
-
added JSON and YAML in the article on “data logger” / data formats on the English Wikipedia
I wonder, whether this modifications will find mercy in the eyes of the “article surveyors”.
- JSON: I attended a presentation given by a member of Pivotal.io, telling of a data logger device, that they use in a project, that emits JSON
- YAML: a huge international web warehouse exchanges its data with its logistics partners in YAM – that is EDI genuine homeland. I personally and directly know of business going on like that.
Yes, I should have quoted both of them, when I added the 2 to the article. But then – what serious proof do I have?
-
checking fetchmail’s log file for sslfingerprint complaints
- https://en.wikipedia.org/wiki/fetchmail
- https://github.com/JochenHayek/misc/blob/master/fetchmail–extract_fingerprints.pl
Having run my log file analyser for a couple of days, I can only tell you, it’s a big relief to know, when sslfingerprints are alright and when they are not and also how to fix them instantly.
I am checking my e-mail not by looking at my dozens of IMAP folders, but I check my e-mail by looking at a procmail log file converted to look like a emacs diary, at least my special version of an emacs diary. My procmail log file “tailf viewer” stalls every now and then, because its “ssh father process” stalls. Right before restarting this procmail log file viewer is the right time to run my fetchmail log file checker.
Sure, I would love to get informed of fetchmail sslfingerprint problems instantly – why not through XMPP, i.e. sendxmpp?!! This kind of problem needs to get addressed w/o undue delay.
Remember: fetchmail mostly runs as a silent demon, fetching and forwarding e-mail, leaving messages in its log file – but who surveys fetchmail’s log file? I don’t think creating messages outside its log file is in the spirit of fetchmail, so there is really no alternative to surveying that log file. Have you already started?
-
my Thursday evening movie at the Sony Center: Fury (2014) – a WWII action drama with Brad Pit
- http://www.imdb.com/title/tt2713180
- http://www.imdb.com/title/tt2713180/faq : Q: How could a single Tiger tank do so much damage to the Shermans? A: …
The Sherman tank was used by the Allies in every theatre of World War 2 and was famed for its’ speed, manouverability, reliability and ease of mass production. However its’ 75/76mm gun was generally incapable of penetrating the main armour of its’ German counterparts, the Panther and Tiger. By contrast the Panther’s 75mm and especially the Tiger’s 88mm could easily defeat the Sherman’s armoured protection as could German infantry anti-tank weapons. The Sherman’s high profile also made it comparatively easy to spot and its’ use of a petrol engine gave it an unfortunate propensity to burst into flames when hit. British and Canadian troops nicknamed them ‘Ronsons’ due to this fact in reference to a brand of cigarette lighters guaranteed to ‘Light every time’. The Germans rather more bluntly referred to them as ‘Tommy cookers’.
I honestly recommend this film – not really as entertainment, but still.
-
Asaf Avidan’s new album “Gold Shadow” – yet another appetizer appeared – and not just on YouTube
What a nice idea: paying for the appetizers now, paying for only the difference of the price of the entire MP3 album, once it’s out.
If I had known before, I would have already gone for that, when I purchased “over my head” a couple of days ago. Well, never really too late. Was only little money then, and this music really helps me keeping going.
-
modifying metadata and “Tags” of your e-books – using calibre
Calibre allows you to edit metadata of your books like e.g. Tags, I call that categories. And I love using categories (from DMOZ.org). But if I change book metadata in calibre, they stay in calibre’s database – until I do “Save to disk” – but then the updated books still go to a separate directory tree – this may be on purpose – but I would rather like to get the books updated “in place”, i.e. the books themselves that I included myself.
Likewise with bookmarks, and “selections”, i.e. “marked areas” – the Mac’s “iBooks” has that feature, calibre not yet, but I wished it had them, because that’s a rather nice feature.
The books will hopefully survive for a while, calibre’s database is rather “transient”, just as iBooks’ database is. That’s the idea.
I quite like iBooks’ nice extra features, like commenting – they drive innovation. But I don’t like the mysterious store, where its memory is kept, i.e. the proprietary database.
