|
| Greg's diary |
|
||||||||
|
|
|
||||||||||||||||
| Wednesday, 1 April 2026 | Today's diary | Today's images | top | next | last |
Another of those day pairs where I do lots of things (yesterday) and spend the whole next day writing up about them (today). I didn't even finish before dinner.
Yvonne into town today, and while she was there she had a growth excised. She was given a sheet of paper, a copy of a message sent to Matthew Pilkington, a colleague of Paul Smith who had presumably written the referral. Diagnosis: "LEFT LATERAL NECK SHAVE NODULAR AND SUPERFICIAL BASAL CELL CARCINOMA” (why do they shout?). Then clinical notes: "Left lateral neck evolving flat red macule ? Bowen's disease”. No mention of a prognosis, and following up shows that Bowen's disease is different from basal-cell carcinoma. The general impression I get is that the matter has been dealt with now, but it would be nice to have some kind of confirmation. The Wikipedia pages suggest that there's not much danger, but why go to a doctor when “I read it on the Internet”?
File system full on fra.lemis.com today. Nothing unusual: it's the web server logs. Rotate (I must really automate this) and compress.
But then I saw a file /var/tmp/webfoo or some such, and it was big (gigabytes) and growing. Where did that come from? lsof to my aid. Oh, no lsof. OK,
=== root@fra (/dev/pts/1) /var/tmp 62 -> pkg install lsof
Updating FreeBSD repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository FreeBSD has no meta file, using default settings
And there it hung. This isn't a very old system (FreeBSD 14.2, not even a year old).
While pondering what to do, compressing the old web log completed. And webfoo went away. Was it a symlink maybe? It had a link count of 1. Strange name to choose, more like something that I might have thought up. But I have no recollection.
No named failures today, but it's only a matter of time. And currently I have no backup, so each failure means an average of 30 minutes with no resolution. Why not do it on fra?
Oh. fra has had a named running since December last year. Copy the latest zone files and try again:
=== root@fra (/dev/pts/1) /usr/local/etc/namedb 115 -> service named restart
named not running? (check /var/run/named/pid).
/usr/local/etc/namedb/named.conf:7: unix control '/var/run/ndc': not supported
/usr/local/etc/rc.d/named: ERROR: named-checkconf for /usr/local/etc/namedb/named.conf failed
There's something very strange about named.
| Thursday, 2 April 2026 | Today's diary | Today's images | top | previous |
So why does named no longer run on fra.lemis.com? Another question for the twins, which indicated that my named.conf is older than the named on fra. OK, fix:
@@ -1,10 +1,12 @@
+include "/usr/local/etc/namedb/rndc.key";
+
controls {
inet * port 52 allow { any; }; // a bad idea
- unix "/var/run/ndc" perm 0600 owner 0 group 0; // the default
+ inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "rndc-key"; };
};
And yes, that fixed it. But BIND is now 40 years old. It's still unstable (version 8 at any rate), and you'd think that the new versions could accommodate the old ones.
One of the things that most irritate me about DxO PhotoLab is that by default cropping an image retains the original aspect ratio, and there's no setting to get rid of it: I have to reset to “unconstrained” every time. But today, for the first time in over 10 years, I found a reason to use it.
Well, not quite. The photo was taken with my OM System OM-1 Mark II and thus had a 4:3 aspect ratio. But Yvonne wanted it on the root window of lagune as a background, so it had to be 16:9. And I was able to set that:
Yvonne has been following the weekly petrol prices. This week they're lower. The government has halved the petrol excise tax, worth about 25¢ per litre:
|
||||||||||||||||||||||||
But look at the image quality. Here a cutout:
|
|
||||||||||
That should be perfectly legible. What went wrong? One thing, of course, is that it was taken with a mobile phone, but it still should be much better than that. To be investigated.
Do you have a comment about something I have written? This is a diary, not a “blog”, and there is deliberately no provision for directly adding comments. It's also not a vehicle for third-party content. But I welcome feedback and try to reply to all messages I receive. See the diary overview for more details. If you do send me a message relating to something I have written, please indicate whether you'd prefer me not to mention your name. Otherwise I'll assume that it's OK to do so.
| Top of page | Greg's home page | Today's diary entry | Greg's photos | Copyright information |
