Die DSL-Router aus Thomsons SpeedTouch-Serie genießen den Ruf, eine ausgezeichnete Modembaugruppe zu haben und außerdem auch als reines Modem betreibbar zu sein. Das war für mich genug Grund, mir mal so ein Gerät aus der Nähe anzugucken.
Continue reading "SpeedTouch 536i"relativ neu: Von Kindern geschraubt die noch weniger wissen als die Alten.
Quelle: Dietz Pröpper in dasr (<2224939.d8E1qJU1S8@rotfl.franken.de>).
relativ neu:Aus n+1 Quellen mit alten Fehlern zusammengestellt.
Quelle: Helmut Springer in dasr (<mT3pqjceIt5fN254@delta.citecs.de>).
Unter dem tag "fdi" veröffentliche ich in loser Folge Fachbegriffe der Informatik im Stile der von Lutz geführten Liste
Alle Artikel aus dieser Gruppe im Blog-Layout gibt es hier; und den RSS-Feed hier.
Zwischen Weihnachten und Neujahr war ich in Berlin auf dem 23. Chaos Communication Congress. Und bin mit gemischten Gefühlen wieder gefahren.
Continue reading "23c3 - Who can you trust"For nearly two years, I have been pondering about a good and failure-resilient DNS setup to implement for my own domains. In the last days, I have set the first prototype into use.
No, I haven't dared to touch zugschlus.de, my most important domain, yet. This is planned for the weekend. So, if you experience difficulties in accessing any of my Internet services, please inform me and allow me to fix the issue.
Continue reading "New DNS setup getting productive"I recently had an issue where a remote host would frequently run out of memory after a number of processes had been invoked from remote. I looked in the wrong direction first, but finally found out that each process invocation leaves two sshd processes hanging around, which are eventually exhausting the memory on the box.
Next step was finding out what happened for the sshd processes not to properly terminate. Eventually, I remembered that the incoming ssh connections were not invoked directly, but via a third host with "proxycommand ssh other-host socket %h %p". Looking on other-host quickly showed a number of socket processes being around, and killing them made the sshds on the low-memory host vanish as well.
Short-term remedy was therefore to set ClientAliveInterval in the low-memory host's sshd configuration.
I then searched for reasons why ClientAliveInterval is not set by default at least in Debian's sshd configuration. I didn't find a reason and proceeded to file a wishlist bug request againnst openesh-server for this option to be set by default.
Before filing this bug, I routinely visited the BTS, just to find out that the bug was already filed. By me. One year and 285 days ago. And that the openssh maintainer(s) didn't even bother to reply to it yet.
Guys, _this_ is a textbook example how to discourage people from filing Bugs against your packages. Please, give them at least the appreciation of a short ACK if you don't get around to fixing the bugs in reasonably short time. Having a bug rot away uncommented and unfixed in the BTS for two years is simpy not acceptable. Yes, that goes even for a wishlist bug.