Skip to main content

Fireworks

It's the Queens Birthday long weekend in Canberra and that means several things. It is not the Queens Birthday (as she was born April 21 1926), monday is a public holiday and we get to buy fireworks!

We are not allowed to buy rockets or firecrackers (also known as bungers) but we can still get some pretty impressive fireworks. There are ones that shoot sparks up into the air, several times higher than a man, there are others that fire a parachute up into the air and, hopefully, it will land in the neighbours pool (who we dislike intensely) and there are others that fire a projectile that explodes.

June in Canberra is getting cold. It is dark by about five and when we set up the fireworks we are normally feeling cold and miserable. A few years ago my eldest son found a way to warm up. He was setting off one of the projectile emitting fireworks and he had backed away a short distance when it started to fire the projectiles. The tube fell over and explosives were fired all over the garden and he had to run for cover. Not a recommended way to warm yourself up. I have the video to prove it!

The serious side to fireworks is the effect they have on pets. I have never had a pet that was pathologically afraid of fireworks. keeping them inside has always seemed to be enough for our dogs. Our cats have never been worried by them even in Kuala Lumpur where the fireworks were readily available and around Chinese New Year fire crackers would go off all the time as every kid would buy them. We had a dog who was terrified of thunder. She was smart enough not to run away as she felt safer with us. Every year there are complaints from pet owners so the problem must be real.

Comments

Popular posts from this blog

The Extended Attributes Are Inconsistent in Windows 8

I have upgraded my laptop to Windows 8 and all was fine for about three hours and then I started to get an error when trying to run any application that required Administrator privileges. Half an hour of Googling led me to this blog post   Case of the broken uac prompt This problem was caused by downloading themes. The final theme I had decided on included a new sound theme. Clearly at least one of the sounds did not play (the one for the UAC prompt!). Changing the sound theme (right click on desktop, choose "personalisation") to Windows Default sorted out the problem. Doing a clean install would also have fixed it but that would have been a drastic solution and as soon as I installed a new theme it may have happened again.

Beware vnc and upnp

My new linux box got hacked yesterday. I was careless. My ADSL router has upnp support and it is turned on by default. I enabled "Remote Desktop" in Linux - which is a version of vnc - and decided not to set a password as it would not be accessible from outside the local network. That was my first mistake. Last night I noticed a second connection to the linux box. Someone was using the browser and had connected to Western Union and was trying to install the flash plugin. They had not got very far as Fedora 14 does not install Flash on a 64bit system as it is still in beta so the install is not straightforward. I was able to disconnect this errant person before they got any further and I then disconnected the ADSL line from the modem to prevent another attempt and proceeded to diagnose what had happened. I checked the preferences for VNC and noticed the automatically configure the network check box had been selected and that it was reporting an external address could be

"No child processes" error on Linux

A problem was reported by a customer. They were getting a failure and in the logs it reported error → waitpid failed 'Reason: No child processes' The “No child processes” error came from waitpid() after using  fork/spawn to launch a utility to load data into a data base. Upon detailed investigation it appears it is possible that some other process that the user is running has changed the default handler for SIGCHLD - possibly the shell (e.g. bash!) used to launch our server processes. If the signal handler is set to SIG_IGN then when a process is started using fork()/exec() the return code from the process is NOT returned and waitpid() cannot retrieve the response code. The most likely reason for "No child processes" error from waitpid() is that the signal handler for child processes (SIGCHLD) is not set to SIG_DFL. This should not be possible however it seems that on Linux a process run in the shell (or maybe a shell process) can set it