July 3rd, 2007

amazon

Ouch, my head...

I'm not sure which is worse to wish for. That I have a headcold, or that I have allergies. If I have a headcold, that means I caught it and could pass it on. If I have allergies, well, I've *never* had seasonal allergies before!

My sinus walls fell like they are about to explode. I am beginning to wish that they would...
amazon

Dear LazyWeb. Very slow login into my FC6 Desktop

I recently upgraded my laptop from FC5 to FC6.

When I graphically login to my account, the login process hangs on a blank grey screen for a couple of minutes, and then proceeds to login normally. If I create a new user account, when I login to it, here is no hang.

It smells like a network or name resolver timeout. I think it's the WM, Metacity, that is hanging. I suspect there is something present or absent in my gconf configuration that's causing it. Howeve, the Gnome people have copied one of Windows bad features, in that the login process and WM and Desktop initialization process is not logged or recorded anywhere.

Anyone else seen this? Is there a simple, or even complex, way to find out whats happening and fix it?

And "just create a new account and use it" isn't an answer.

Clues?
amazon

Productive? Maybe. Crashing net-snmp.

I don't know how effectively productive I was today, but I did discover that it's possible to make net-snmp 5.4 crash with a sigseg by sending it what I think is valid AgentX commands.

Of course, it shouldn't crash and sigseg, ever. Even if you pour utter garbage sent to the AgentX port.

This implies that net-snmp running all over the world could be crashed and possibly even powned via AgentX, which is Not Good, given that the AgentX sockets tend to be all-writable, and snmpd tends to run as root.