yaleman.org

A cute little fireplace!

No code today, just a little brown starship for exploring the galaxy 🙂

I did nine knee-push-ups in a row this morning.

Doesn’t sound like many, until you realise I couldn’t do one to start with without taking a breather.

My upper body strength sucks, but I’ve been doing a Beginner Bodyweight workout for a few weeks every second day (or so, depending on what else I did) and I’m already noticing stark improvements. I wake up at about 5am most mornings (thanks, tiny puppy) then I get my ass down stairs and do some workouts, or some weeding.

Every time I was running apt-get update I’d be asked to select the Area and Town/Zone my timezone was in, as part of the dpkg-reconfigure tzdata step.

If you run the command debconf-set-selections you can configure debconf’s internal database to store the defaults for the future.

The «EOF allows you to keep adding information until EOF is entered by itself on a line. This’ll set a few things - make sure you know which area and zone you want to use (you’ll have seen it when you get asked by tzdata).

Here’s the recipe for port forwarding on a cisco device - this is tested on a Cisco 877, but should work on any of the 800 series, 837, 887 etc etc. Anything that does NAT…

So if I wanted to send TCP traffic to port 125 on my router’s external adsl interface from the internet, and it show up on port 25 of the internal ip 10.0.0.2, I’d do:

On the Cisco 877 there is no default way to to fine tune the SNR margin if you are having stability issues.

There’s a diagnostics tweak which can be enabled to allow modification of the noise margin buffer. Be aware that making this change will instantly drop the connection.

Go into configuration mode and type the following, replacing x with a value between negative three and positive three (-3 -> 3)

Here’s our victim for the day, a busted old toilet roll holder, held together with tape.

Remove tape, fall apart. This is why we’re replacing you, faded old piece of junk! One obvious screw (stripped thread, of course) to remove…

And it looks like we’re finding some sediment-layer-type history here… why bother removing something when you can paint over it?

To check how many events have not been acknowledged via the command line, there’s an SQL query that can be run. You’ll need to login as the mazu user to your profiler and run the command.

psql mazu postgres -c “query goes here”

The field we’re looking for is called ack and is in either of the events tables. The current events are events.current_summary and completed ones are events.old_summary.

To get the number of open, un-acknowledged events, the command is as follows: