The title says it all. There are some very big things in the works. That's all I have time to say now. The big things are keeping me busy.

Oh, and there was some breakage around the site. That's all better. Oops.

I'm developing and building out some really really cool nerd-stuffs right now.

The hardware list in my new stuff (mostly accurate) is available: here [userlame.com].

Also I apparently substitute emoticons before links - a link with "colon capital O" in it breaks horribly.

I don't like yahoo very much these days. They are (were) a minor but annoying thorn in my side. Lemme splain.

Yahoo has this nice feature for its email client called a vacation response. Basically you type in what you want it to say - "out of the office riding goats" or whathaveyou, and when someone sends an email to your account it sends back an email with the subject "Yahoo! Auto Response" - the text of the email contains "out of the office riding goats" or whatever you typed in.

Great. I can tell people I'm not going to read their email for a while. Whoopie.

Some flaws (besides the obvious AUTO-RESPONSES ARE EVIL. DO NOT USE THEM):

1) It doesn't keep track of who it has sent a response to. If I sent two emails to an account with that activiated, I'd get two "Yahoo! Auto Response" replies. Not terrible, though it could possibly lead to some funny mail loops.

2) It's really easy to set up a yahoo account. It would be pretty easy to script an account setup that would present just the captchas to be solved. Then the script could set up an auto-response.

3) No anti-spam policies at all seem to be applied to email that will be auto-responded to. At least I know they aren't checking SPF.

Mix em all together and you get a delicious spam pie. I've written a proof of concept (not a script, you'll have to do it by hand - the rest is an exercise I'll kill the reader for following) so you can see it in action. Try it yourself [userlame.com]. But please, have some netiquette.

In short, spammers are sending email to fake accounts with spam vacation responses. They are faking lots and lots of from addresses on those emails and the spam vacation response is sent to the faked from address. Thus, I end up with a buttload of spam.

It also is completely valid mail. It comes from otherwise (I guess) sane outbound mailservers for yahoo. The email will have a valid domain DomainKey-Signature and everything. It was getting by all my anti-spam because it looks so real.

And so finally, a resolution...spamassassin. Here's a simple rule to send all that crap where it belongs. Adjust the score accordingly if you need to.

header YAHOO_AUTORESPONSE_SPAMZ Subject =~ /^Yahoo! Auto Response$/
score YAHOO_AUTORESPONSE_SPAMZ 5.0
describe YAHOO_AUTORESPONSE_SPAMZ Yahoo auto-response spam

I'm going to bed.

Edit: Yikes, that link was broken. Originally it was .html, and I moved it to .php but didn't update the link. My browser had the .html cached so I never noticed. Sigh.

Well well, it actually just got much easier [internetcommunications.tmcnet.com] to abuse this.

Just so I won't forget and maybe google will spider this and it'll help somebody. There's a (kinda) bug [bugs.gentoo.org] in gentoo's 2007.0 stage3. I'm using amd64, but it's due to the version of ssh which was put into the stage3, so I'm sure it's across platforms. /etc/skel/.ssh is created with permissions 0600 - so when you add a user, by default they won't be able to cd to ~/.ssh. That's a problem when using ssh keys and it frustrated me for a few minutes because I couldn't login in to new servers.

Fix by the following:


After this any new users can use their .ssh directory. If you've already added users and are having problems here's a quick fix:

Just so I won't forget and maybe google will spider this and it'll help somebody. There's a (kinda) bug [bugs.gentoo.org] in gentoo's 2007.0 stage3. I'm using amd64, but it's due to the version of ssh which was put into the stage3, so I'm sure it's across platforms. /etc/skel/.ssh is created with permissions 0600 - so when you add a user, by default they won't be able to cd to ~/.ssh. That's a problem when using ssh keys and it frustrated me for a few minutes because I couldn't login in to new servers.

Fix by the following:


After this any new users can use their .ssh directory. If you've already added users and are having problems here's a quick fix:

I meant to post this a while ago, but never got around to it. If you've purchased a ZyXEL GS2024, and it came with firmware V3.8(LT.0)C0 I pity you. I too bought this lovely lemon. Long story short, it sucked. I was really disappointed when I had my new switch running for about 5 minutes and thought I had to RMA it.

I pulled it out of the box, fired it up, and started playing with it, and no sooner had I upped the serial baud rate when the hardware error light came on. Then it started flashing. Not steadily either, just random on/off. The second command I checked out was reading the logs. I found a whooole bunch of errors in the log about the fan dropping below threshold and recovering (many times per second). From running the diagnostics on the switch the fan was peachy. Sigh.

I checked for new firmware, but this was the most recent. So recent in fact (I thought) that it wasn't even on the manufacturer's site. The manual for 3.8 was there and released only weeks before. I'm sure they actually pulled the firmware down when they realized what a bad bug it had. I googled around and found someone else complaining of the same errors after upgrading from 3.6 to 3.8. I can't find the site now, which is weird. I was there numerous times and posted on it. Hm. I'd post the log messages from the switch, but mine are gone and the only place I knew that had them was that site.

Anyway, I downgraded the firmware and have been playing around with it while running version 3.6. The only feature that I noticed was missing was the ability to use ssh keys. I also noticed logging in as admin wasn't automatically in enable mode in the earlier version. Whatever.

Well, earlier this month, ZyXEL put out a bugfixed version of 3.8 which is available on their site [us.zyxel.com]. If you were one of the lucky ones to get your GS-2024 shipped with firmware V3.8(LT.0)C0 - well, hopefully you've downgraded, but now you can go get a better (read: working) version of 3.8. The version name is very similar - V3.8(LT.1)C0

I would like to point out that it's a very nice switch and I'm quite pleased with it now. ZyXEL was very fast with a fix, but it was disappointing that a bug so painfully obvious was put out, and loaded on production models. Running it for more than a minute or two showed the problem.

Update: Found the forum post I was talking about here [fixya.com]. The fan log messages looked like:

I meant to post this a while ago, but never got around to it. If you've purchased a ZyXEL GS2024, and it came with firmware V3.8(LT.0)C0 I pity you. I too bought this lovely lemon. Long story short, it sucked. I was really disappointed when I had my new switch running for about 5 minutes and thought I had to RMA it.

I pulled it out of the box, fired it up, and started playing with it, and no sooner had I upped the serial baud rate when the hardware error light came on. Then it started flashing. Not steadily either, just random on/off. The second command I checked out was reading the logs. I found a whooole bunch of errors in the log about the fan dropping below threshold and recovering (many times per second). From running the diagnostics on the switch the fan was peachy. Sigh.

I checked for new firmware, but this was the most recent. So recent in fact (I thought) that it wasn't even on the manufacturer's site. The manual for 3.8 was there and released only weeks before. I'm sure they actually pulled the firmware down when they realized what a bad bug it had. I googled around and found someone else complaining of the same errors after upgrading from 3.6 to 3.8. I can't find the site now, which is weird. I was there numerous times and posted on it. Hm. I'd post the log messages from the switch, but mine are gone and the only place I knew that had them was that site.

Anyway, I downgraded the firmware and have been playing around with it while running version 3.6. The only feature that I noticed was missing was the ability to use ssh keys. I also noticed logging in as admin wasn't automatically in enable mode in the earlier version. Whatever.

Well, earlier this month, ZyXEL put out a bugfixed version of 3.8 which is available on their site [us.zyxel.com]. If you were one of the lucky ones to get your GS-2024 shipped with firmware V3.8(LT.0)C0 - well, hopefully you've downgraded, but now you can go get a better (read: working) version of 3.8. The version name is very similar - V3.8(LT.1)C0

I would like to point out that it's a very nice switch and I'm quite pleased with it now. ZyXEL was very fast with a fix, but it was disappointing that a bug so painfully obvious was put out, and loaded on production models. Running it for more than a minute or two showed the problem.

Update: Found the forum post I was talking about here [fixya.com]. The fan log messages looked like:

Long story, buckle up.

So I'm building a new server. Nothing fancy, but eventually I'd like this box to take over for the server that's running this site. So I'm trying to actually do stuff up right, have real redundancy, harden the server some, etc. The box has been sitting around for a while just minus HDDs and PSU, and those I got. I picked up a couple identical small disks and want to do mirroring for redundancy. This site has been hobbling along on a wing and a prayer, and (fingers crossed) no data loss yet. Yet. I'd like to keep it that way. I also decided I'm going to give FreeBSD a shot. Supposedly it has great performance under load, is way stable, and a host of other good things. Now, I don't know crap about BSD and that's actually a big part of why I'm using it. userlame likes to learn.

Parts arrived and I got to putting things together when, genius that I am, I toasted the motherboard. Oops. Ok, so now I'm waiting on a new mobo. While I'm waiting, I decided I'd do some test installing and BSD learning and such on a VM. Well I've finally gotten the install part down now, and that's what this post is about. The actual install is easy as pie. Add mirroring into the mix, and it gets a bit ugly.

So. I learned about these "slices" and "partitions" BSD uses -- it's much different than anything I've dealt with before -- and I kind of have a handle on what's going on. I decided I'm going to have my disk layout as such: each disk with a single slice and partitions laid out like so:

/ (root) - mirrored between drives
swap - striped between drives
/tmp - striped
/usr - mirrored
/var - mirrored
/var/log - mirrored
/home - mirrored

Getting through the install process is easy like I said. I can very quickly get one disk partitioned and do a minimal install that takes about 20 seconds. But where do I go from here once I have one disk layed out correctly (how to mirror)? After monkeying around for hours on end, here's how I did it:

Note: The way I do this is likely very wrong and I don't advocate anyone follow these directions. Really, I don't know what I'm doing wrt BSD.

First, I installed everything to one disk. Then, I just ran through the exact same install process on the other disk. I found this was the easiest way to get things partitioned and correct bsdlabels on each disk slice. At this point the disk looks like this:

ad0s1a - /
ad0s1b - swap
ad0s1d - /var
ad0s1e - /tmp
ad0s1f - /usr
ad0s1g - /var/log
ad0s1h - /home

And the other disk is exactly the same, just ad1 instead of ad0. Now I ran into a chicken and egg problem. I couldn't get gmirror to label (or insert) a mounted partition. I set sysctl kern.geom.debugflags=16 and that didn't help. I also couldn't use gmirror when booted from the cd (different version of some sort missing a lot of functionality it seemed). I tried about a katrillion things before I came up with a solution.

First, I booted to ad0 which gave me a running system with all the above partitions. Then I got gmirror into the mix with "gmirror load". Then, for each mirror I wanted (root, var, usr, varlog, home) I labeled the second disk's partitions. For example the root partition was "gmirror label -v -b round-robin root /dev/ad1s1a" and /usr was "gmirror label -v -b round-robin usr /dev/ad1s1f". After doing this for each partition I had a device in /dev/mirror for each label name - such as /dev/mirror/root.

Next, I wiped those mirrors and layed out a new filesystem on each of them like "newfs -O2 -U /dev/mirror/usr". Next, I mounted the new mirror filesystems into /mnt/labelname such as "mkdir /mnt/varlog" then "mount /dev/mirror/varlog /mnt/varlog". After all the mirrors were mounted, I dumped the live filesystems into them like "dump -L -0 -f- /home | (cd /mnt/home && restore -r -v -f-)". After dumping each one, I unmounted the filesystem and removed the /mnt/labelname directory to be sure things went smooth.

One special note: while I had /mnt/root mounted and after running "dump -L -0 -f- / | (cd /mnt/root && restore -r -v -f-)" I needed to edit /etc/fstab and /boot/loader.conf before rebooting, so I edited these on both the live filesystem and the mnt'd filesystem. In /etc/fstab (and /mnt/root/etc/fstab), I changed everything from the real partitions (such as /dev/ad0s1a and /dev/ad0s1g) to the mirrored partitions (such as /dev/mirror/root and /dev/mirror/varlog). In /boot/loader.conf (and /mnt/root/boot/loader.conf - both empty files) I simply added the line geom_mirror_load="YES". I finished umounting /mnt/root (it was the last one I did), and rebooted. Sure enough, on rebooting I was running on my mirrored filesystems! :

/dev/mirror/root on / (ufs, local)
devfs on /dev (devfs, local)
/dev/mirror/home on /home (ufs, local, soft-updates)
/dev/ad0s1e on /tmp (ufs, local, soft-updates) [Still on real disk; we'll get there]
/dev/mirror/usr on /usr (ufs, local, soft-updates)
/dev/mirror/var on /var (ufs, local, soft-updates)
/dev/mirror/varlog on /var/log (ufs, local, soft-updates)

But hold on, they aren't really mirrored yet. They're still only running on one disk. Now that the partitions on ad0s1 aren't being mounted however, it's a simple matter to add those partitions to the mirror. Examples: "gmirror insert -v root /dev/ad0s1a" and "gmirror insert -v home /dev/ad0s1h". And ta-da that's it! A mirrored filesystem! (I don't have [code] tags so this formatting will be nasty):

# gmirror status
         Name       Status    Components
  mirror/root     COMPLETE    ad0s1a
                                        ad1s1a
   mirror/var     COMPLETE    ad0s1d
                                        ad1s1d
   mirror/usr     COMPLETE    ad0s1f
                                        ad1s1f
mirror/varlog     COMPLETE    ad0s1g
                                        ad1s1g
  mirror/home     COMPLETE    ad0s1h
                                        ad1s1h


I know I mentioned something about doing striping earlier though, so let's get to that. Once I had the mirroring stuff under my belt, this wasn't so tough. Let's do the swap first. We can't use any partitions that are in use so first we have to turn swap off. No problem. "swapoff -a". Then we just create the stripe - "gstripe load" to turn it on and "gstripe label -v swap /dev/ad0s1b /dev/ad1s1b" and that's it! "swapon /dev/stripe/swap" and we're in business. Don't forget to update /etc/fstab with the new swap device as well. /tmp isn't much harder. Just a "umount /tmp" followed by "gstripe label -v tmp /dev/ad0s1e /dev/ad1s1e" and that's done. Change that in /etc/fstab as well. Just one more thing to do - update /boot/loader.conf to load striping as well. Add the line (only contains our 1 line from earlier now) geom_stripe_load="YES" and that's it.

A reboot later, and I'm running with striped swap and /tmp, and the rest of my filesystems are mirrored. And it only took the better part of 9 hours to get there!

I also found an interesting and very frustrating bug while doing this. I've run it to it randomly before, but never been able to reproduce it or guess what caused it. Apparently beryl runs out of video memory. It's possible that it's an application that's running, but I'm not sure which one it would be. I haven't found a common thread between times I've seen this. When it happens, any new windows that are opened are completely black inside. My guess is that there's no memory to create the new window. Now, a stupid side effect that seems to happen at the same time is this is that switching to my fourth virtual desktop from my first virtual desktop (only this move seems to do it) will kill whatever application had focus when I moved.

The problem with this discovery was how I found it. If I didn't have the keyboard locked by the virutal machine, and I was in the installer process of BSD, it would start a shell on vty4. So to get to that, I had to hit Alt+F4. Well it just so happens that if I forget to specifically focus on the virtual machine, I'd end up moving to virtual desktop 4 and killing the VM. And I did that so. many. times. It was frustrating. That added a lot of time.

Edit: Found the culprit. It's Azureus somehow eating up video memory. If I run it for more than a few hours I start getting this. Ending Azureus and all java processes does not release the memory back. Kind of a weird bug (doesn't appear Azureus specific with the aforementioned symptoms).

So I was going to write a howto for using openchrome on my averatec AV2260EH1-R. I never got around to doing that, and now I need to update my kernel and really wish I had. This thread is just a reminder to myself to do that this time.

So I was going to write a howto for using openchrome on my averatec AV2260EH1-R. I never got around to doing that, and now I need to update my kernel and really wish I had. This thread is just a reminder to myself to do that this time.

I've spent the last day and a half intermittantly trying to track down a bug I was hitting when restarting apache2. Buckle up, this is going to be a long problem explanation.

Basically, I was seeing incredibly slow startup times of apache. It could be from 30 seconds up to 5 minutes or more. And it wasn't just starting apache; it was slow stopping apache (-k stop), starting apache (-k start), and even testing the config (-t).

That's weird, but it gets weirder. This problem would only randomly (pun intended; read on) appear. Apache would restart just fine, and then I'd restart it again later and it would hang. Even the problem itself didn't remain the same. Some times it would get through configtest ok and hang at stop and start (or graceful). Sometimes it would get through configtest and stop and then hang on start. It also hung two places on starting. First it would block and hang immediately, then it would background and open a listen socket on 80 but block and hang before it started worker processes. You could connect to the server and send requests, but there you'd sit with no workers to service you. Now randomly mash together some of these places where it could hang and that's what I'd see. And not consistently; sometimes it was just fine.

I'm running gentoo and was using the init script /etc/init.d/apache2 to restart the server. I confirmed it wasn't the init scripts hanging by first running apache2ctl directly, then going straight to the apache2 binary. Same deal with all of them. I went through everything that I could think of that could be causing it. I'd never seen this problem before. I ran into the problem after installing mod_perl, but the issue remained after reverting everything to it's original state. I spent a lot of time believing that had caused it.

I'm going to skip all the crazy googling and wild goose chasing I did. I put my configs into all state of disarray even trying to isolate the problem.

Fast forward about 24 hours - in a strange moment of clarity I realized that I had run an strace on the init and apachectl scripts which didn't really show me much, but hadn't done an strace directly on apache2 (which would obviously give me better info). So I traced a configtest (strace /usr/sbin/apache2 -DPHP5 -DPERL -DDEV -d/usr/lib/apache2 -f/etc/apache2/httpd.conf -t) a couple times, until it hung. And there it was right before my eyes:



It was opening /dev/random and blocking! Shit! I confirmed that this was the problem by cat /proc/sys/kernel/random/entropy_avail and it was something like 33. I was short on entropy. Why it wasn't using urandom I didn't know, but armed with my new knowledge I hit google again and found this article [raptorized.com]. It pretty well explains it at the end...I stuck urandom into my USE flags in make.conf (surprised this isn't a default flag I guess), and re-emerged dev-libs/apr. Bam, problem gone.

Phew, that kinda sucked. The scoop is I'm working on my dev server porting the new site to mod_perl. Yeah right, that will help me actually work on it.

I've spent the last day and a half intermittantly trying to track down a bug I was hitting when restarting apache2. Buckle up, this is going to be a long problem explanation.

Basically, I was seeing incredibly slow startup times of apache. It could be from 30 seconds up to 5 minutes or more. And it wasn't just starting apache; it was slow stopping apache (-k stop), starting apache (-k start), and even testing the config (-t).

That's weird, but it gets weirder. This problem would only randomly (pun intended; read on) appear. Apache would restart just fine, and then I'd restart it again later and it would hang. Even the problem itself didn't remain the same. Some times it would get through configtest ok and hang at stop and start (or graceful). Sometimes it would get through configtest and stop and then hang on start. It also hung two places on starting. First it would block and hang immediately, then it would background and open a listen socket on 80 but block and hang before it started worker processes. You could connect to the server and send requests, but there you'd sit with no workers to service you. Now randomly mash together some of these places where it could hang and that's what I'd see. And not consistently; sometimes it was just fine.

I'm running gentoo and was using the init script /etc/init.d/apache2 to restart the server. I confirmed it wasn't the init scripts hanging by first running apache2ctl directly, then going straight to the apache2 binary. Same deal with all of them. I went through everything that I could think of that could be causing it. I'd never seen this problem before. I ran into the problem after installing mod_perl, but the issue remained after reverting everything to it's original state. I spent a lot of time believing that had caused it.

I'm going to skip all the crazy googling and wild goose chasing I did. I put my configs into all state of disarray even trying to isolate the problem.

Fast forward about 24 hours - in a strange moment of clarity I realized that I had run an strace on the init and apachectl scripts which didn't really show me much, but hadn't done an strace directly on apache2 (which would obviously give me better info). So I traced a configtest (strace /usr/sbin/apache2 -DPHP5 -DPERL -DDEV -d/usr/lib/apache2 -f/etc/apache2/httpd.conf -t) a couple times, until it hung. And there it was right before my eyes:



It was opening /dev/random and blocking! Shit! I confirmed that this was the problem by cat /proc/sys/kernel/random/entropy_avail and it was something like 33. I was short on entropy. Why it wasn't using urandom I didn't know, but armed with my new knowledge I hit google again and found this article [raptorized.com]. It pretty well explains it at the end...I stuck urandom into my USE flags in make.conf (surprised this isn't a default flag I guess), and re-emerged dev-libs/apr. Bam, problem gone.

Phew, that kinda sucked. The scoop is I'm working on my dev server porting the new site to mod_perl. Yeah right, that will help me actually work on it.

Ah to be young again...

Session Start: Tue Feb 26 18:44:15 2002
Session Ident: NICKNAME (MACHINE@HOSTNAME)
[02/26-18:44] <NICKNAME> any good at mirc scripting
[02/26-18:45] <userlame> wuddya need?
[02/26-18:45] <NICKNAME> I want to have one nick unopped ok
[02/26-18:46] <userlame> k...
[02/26-18:46] <NICKNAME> so that each time it receives a spam it will auto msg NICKNAME, and on receipt of that message notice or whatever NICKNAME will kick ban the spammer
[02/26-18:46] <NICKNAME> with me
[02/26-18:47] <userlame> a spam as in...do u want a msg filter for a bot or just an auto-msg on any msg?
[02/26-18:47] <NICKNAME> auto msg on any message
[02/26-18:47] <userlame> that's not too hard...
[02/26-18:48] <NICKNAME> can u do it for me,,
[02/26-18:48] <NICKNAME> one for the non opped nick that auto sends the kickban msg to the opped one
[02/26-18:48] <userlame> sure....does ur bot have a variable for ur nick so it knows who u are and whether or not ur on?
[02/26-18:48] <userlame> ok.
[02/26-18:49] <NICKNAME> no bots
[02/26-18:50] <NICKNAME> 2 basic mircs,,
[02/26-18:50] <NICKNAME> one is opped as NICKNAME
[02/26-18:50] <NICKNAME> one is unopped as OTHERNICKNAME
[02/26-18:50] <NICKNAME> as spammers wont message any nick thats opped. so only way to catch them is this way
[02/26-18:51] <userlame> ok...just put in the remote of the other one ON 1:TEXT:*:?:/msg NICKNAME $1-
[02/26-18:51] <NICKNAME> actually beter name for unopped one is ALTNICKNAME
[02/26-18:51] <userlame> that will send u every private msg it gets.
[02/26-18:51] <NICKNAME> yes
[02/26-18:52] <NICKNAME> and then it auto kickbans
[02/26-18:52] <NICKNAME> the mesage will be to activate the kickban on that user
[02/26-18:53] <userlame> k...do you have a particular kick/ban style of script u usually use? like a certain level of the user mask?
[02/26-18:55] <NICKNAME> no
[02/26-18:55] <NICKNAME> basic mirc,,no frills.
[02/26-18:55] <NICKNAME> no scripts no addons
[02/26-18:55] <NICKNAME> hopefully no back dorrs
[02/26-18:57] <userlame> k, imma write this out in a little text file and send it if that's alright.
[02/26-19:00] <NICKNAME> cool
[02/26-19:07] <userlame> lemme try a test run of sorts and i'll send it over.
[02/26-19:08] <NICKNAME> ok
[02/26-19:16] <userlame> ok try this...
[02/26-19:17] <NICKNAME> k
[02/26-19:17] <userlame> after you get it put in just let me know who the spammer checker person is and i'll try msg'ing them. we'll see if it kicks my ass.
[02/26-19:18] <userlame> oh, and if u want i could put in something so it won't fuq with the ops if they msg it or whatever.
[02/26-19:19] <NICKNAME> try a msg to ALTNICKNAME now so.
[02/26-19:19] <userlame> k
[02/26-19:19] <userlame> it's got some ignore script running
[02/26-19:19] <userlame> [02/26-19:19] -ALTNICKNAME- I am using a secure query event. You will be notified if accepted. Until then your msgs will be ignored.
[02/26-19:20] <NICKNAME> turned it off
[02/26-19:20] <NICKNAME> try now.
[02/26-19:20] <userlame> k
[02/26-19:20] <userlame> hm. did it do anything?
[02/26-19:21] <NICKNAME> didnt kick u ?
[02/26-19:21] <NICKNAME> grr
[02/26-19:21] <userlame> did it msg u?
[02/26-19:21] <NICKNAME> ON 999:TEXT:..spammer*:?:{
[02/26-19:21] <NICKNAME> ALTNICKNAME is name.
[02/26-19:21] <NICKNAME> whow me what it should be using that
[02/26-19:24] <userlame> ?
[02/26-19:25] <userlame> u put in the stuff in for ur remote and user sections and in ALTNICKNAME's remote?
[02/26-19:25] <NICKNAME> try now I forgot to change that and enter the nick,
[02/26-19:25] <userlame> ok.
[02/26-19:25] <NICKNAME> soon as u msg it u should get kicked
[02/26-19:26] <userlame> ya.
[02/26-19:26] <NICKNAME> [01:21] <ALTNICKNAME> ..spammer userlame
[02/26-19:26] <userlame> did it msg u when i msg'd it?
[02/26-19:26] <userlame> ok.
[02/26-19:26] <NICKNAME> didnt kick u?
[02/26-19:26] <userlame> and did you get anything echo'd to ur status or to ur active window?
[02/26-19:26] <NICKNAME> it should have auto kickban
[02/26-19:26] <NICKNAME> [01:21] <userlame> la la
[02/26-19:27] <userlame> did u put the stuff into ur remote from that txt?
[02/26-19:27] <NICKNAME> yes
[02/26-19:27] <NICKNAME> let me copy back what I put in ok,,
[02/26-19:27] <userlame> k
[02/26-19:27] <NICKNAME> ON 999:TEXT:..ALTNICKNAME*:?:{
[02/26-19:27] <NICKNAME> if ($2 ison #CHANNEL) {
[02/26-19:27] <NICKNAME> }
[02/26-19:27] <NICKNAME> else {
[02/26-19:27] <NICKNAME> }
[02/26-19:27] <NICKNAME> }
[02/26-19:28] <userlame> (and there were no msg's put in ur status window or anything like /if: insufficient paramaters or anything?)
[02/26-19:28] <NICKNAME> ON 999:TEXT:..ALTNICKNAME*:?:{
[02/26-19:28] <NICKNAME> if ($2 ison #adultnetmeeting) {
[02/26-19:28] <NICKNAME> }
[02/26-19:28] <NICKNAME> else {
[02/26-19:28] <NICKNAME> }
[02/26-19:28] <NICKNAME> }
[02/26-19:28] <userlame> oh oh...
[02/26-19:28] <NICKNAME> -
[02/26-19:28] <NICKNAME> -
[02/26-19:28] <NICKNAME> * /ban: no such user $mask($2,3)
[02/26-19:28] <userlame> hm.
[02/26-19:28] <NICKNAME> was in status
[02/26-19:28] <userlame> ok try this.
[02/26-19:29] <userlame> the first line should be ON 999:TEXT:..spammer*:?:{
[02/26-19:29] <userlame> that should fix it.
[02/26-19:29] <NICKNAME> done
[02/26-19:29] <NICKNAME> try now.
[02/26-19:29] <userlame> k
[02/26-19:30] <userlame> there we go.
[02/26-19:30] <NICKNAME> cool
[02/26-19:30] <NICKNAME> worked fine
[02/26-19:30] <userlame> now u can just change the "add ur kick reason here" to the reason you want put in.
[02/26-19:30] <userlame> and it's set.
[02/26-19:31] <NICKNAME> i did just now.
[02/26-19:31] <userlame> then unban me and we'll call it even. :Ş
[02/26-19:32] <NICKNAME> just did,,
[02/26-19:32] <userlame> hehe thnx.
[02/26-19:34] <NICKNAME> last test
[02/26-19:34] <NICKNAME> make sure changes I made are ok
[02/26-19:34] <userlame> k.
[02/26-19:35] <userlame> a-ok.
[02/26-19:35] <NICKNAME> cool
[02/26-19:35] <NICKNAME> man u know this stuff real well
[02/26-19:36] <NICKNAME> wouldm have taken me ages
[02/26-19:36] <NICKNAME> if at all LOL
[02/26-19:36] <userlame> i've been doing it for 6 yrs now on and off.
[02/26-19:36] <userlame> hehe
[02/26-19:36] <userlame> i'm a nerd.
[02/26-19:36] <userlame> hehe
Session Close: Tue Feb 26 19:52:25 2002

Ah to be young again...

Session Start: Tue Feb 26 18:44:15 2002
Session Ident: NICKNAME (MACHINE@HOSTNAME)
[02/26-18:44] <NICKNAME> any good at mirc scripting
[02/26-18:45] <userlame> wuddya need?
[02/26-18:45] <NICKNAME> I want to have one nick unopped ok
[02/26-18:46] <userlame> k...
[02/26-18:46] <NICKNAME> so that each time it receives a spam it will auto msg NICKNAME, and on receipt of that message notice or whatever NICKNAME will kick ban the spammer
[02/26-18:46] <NICKNAME> with me
[02/26-18:47] <userlame> a spam as in...do u want a msg filter for a bot or just an auto-msg on any msg?
[02/26-18:47] <NICKNAME> auto msg on any message
[02/26-18:47] <userlame> that's not too hard...
[02/26-18:48] <NICKNAME> can u do it for me,,
[02/26-18:48] <NICKNAME> one for the non opped nick that auto sends the kickban msg to the opped one
[02/26-18:48] <userlame> sure....does ur bot have a variable for ur nick so it knows who u are and whether or not ur on?
[02/26-18:48] <userlame> ok.
[02/26-18:49] <NICKNAME> no bots
[02/26-18:50] <NICKNAME> 2 basic mircs,,
[02/26-18:50] <NICKNAME> one is opped as NICKNAME
[02/26-18:50] <NICKNAME> one is unopped as OTHERNICKNAME
[02/26-18:50] <NICKNAME> as spammers wont message any nick thats opped. so only way to catch them is this way
[02/26-18:51] <userlame> ok...just put in the remote of the other one ON 1:TEXT:*:?:/msg NICKNAME $1-
[02/26-18:51] <NICKNAME> actually beter name for unopped one is ALTNICKNAME
[02/26-18:51] <userlame> that will send u every private msg it gets.
[02/26-18:51] <NICKNAME> yes
[02/26-18:52] <NICKNAME> and then it auto kickbans
[02/26-18:52] <NICKNAME> the mesage will be to activate the kickban on that user
[02/26-18:53] <userlame> k...do you have a particular kick/ban style of script u usually use? like a certain level of the user mask?
[02/26-18:55] <NICKNAME> no
[02/26-18:55] <NICKNAME> basic mirc,,no frills.
[02/26-18:55] <NICKNAME> no scripts no addons
[02/26-18:55] <NICKNAME> hopefully no back dorrs
[02/26-18:57] <userlame> k, imma write this out in a little text file and send it if that's alright.
[02/26-19:00] <NICKNAME> cool
[02/26-19:07] <userlame> lemme try a test run of sorts and i'll send it over.
[02/26-19:08] <NICKNAME> ok
[02/26-19:16] <userlame> ok try this...
[02/26-19:17] <NICKNAME> k
[02/26-19:17] <userlame> after you get it put in just let me know who the spammer checker person is and i'll try msg'ing them. we'll see if it kicks my ass.
[02/26-19:18] <userlame> oh, and if u want i could put in something so it won't fuq with the ops if they msg it or whatever.
[02/26-19:19] <NICKNAME> try a msg to ALTNICKNAME now so.
[02/26-19:19] <userlame> k
[02/26-19:19] <userlame> it's got some ignore script running
[02/26-19:19] <userlame> [02/26-19:19] -ALTNICKNAME- I am using a secure query event. You will be notified if accepted. Until then your msgs will be ignored.
[02/26-19:20] <NICKNAME> turned it off
[02/26-19:20] <NICKNAME> try now.
[02/26-19:20] <userlame> k
[02/26-19:20] <userlame> hm. did it do anything?
[02/26-19:21] <NICKNAME> didnt kick u ?
[02/26-19:21] <NICKNAME> grr
[02/26-19:21] <userlame> did it msg u?
[02/26-19:21] <NICKNAME> ON 999:TEXT:..spammer*:?:{
[02/26-19:21] <NICKNAME> ALTNICKNAME is name.
[02/26-19:21] <NICKNAME> whow me what it should be using that
[02/26-19:24] <userlame> ?
[02/26-19:25] <userlame> u put in the stuff in for ur remote and user sections and in ALTNICKNAME's remote?
[02/26-19:25] <NICKNAME> try now I forgot to change that and enter the nick,
[02/26-19:25] <userlame> ok.
[02/26-19:25] <NICKNAME> soon as u msg it u should get kicked
[02/26-19:26] <userlame> ya.
[02/26-19:26] <NICKNAME> [01:21] <ALTNICKNAME> ..spammer userlame
[02/26-19:26] <userlame> did it msg u when i msg'd it?
[02/26-19:26] <userlame> ok.
[02/26-19:26] <NICKNAME> didnt kick u?
[02/26-19:26] <userlame> and did you get anything echo'd to ur status or to ur active window?
[02/26-19:26] <NICKNAME> it should have auto kickban
[02/26-19:26] <NICKNAME> [01:21] <userlame> la la
[02/26-19:27] <userlame> did u put the stuff into ur remote from that txt?
[02/26-19:27] <NICKNAME> yes
[02/26-19:27] <NICKNAME> let me copy back what I put in ok,,
[02/26-19:27] <userlame> k
[02/26-19:27] <NICKNAME> ON 999:TEXT:..ALTNICKNAME*:?:{
[02/26-19:27] <NICKNAME> if ($2 ison #CHANNEL) {
[02/26-19:27] <NICKNAME> }
[02/26-19:27] <NICKNAME> else {
[02/26-19:27] <NICKNAME> }
[02/26-19:27] <NICKNAME> }
[02/26-19:28] <userlame> (and there were no msg's put in ur status window or anything like /if: insufficient paramaters or anything?)
[02/26-19:28] <NICKNAME> ON 999:TEXT:..ALTNICKNAME*:?:{
[02/26-19:28] <NICKNAME> if ($2 ison #adultnetmeeting) {
[02/26-19:28] <NICKNAME> }
[02/26-19:28] <NICKNAME> else {
[02/26-19:28] <NICKNAME> }
[02/26-19:28] <NICKNAME> }
[02/26-19:28] <userlame> oh oh...
[02/26-19:28] <NICKNAME> -
[02/26-19:28] <NICKNAME> -
[02/26-19:28] <NICKNAME> * /ban: no such user $mask($2,3)
[02/26-19:28] <userlame> hm.
[02/26-19:28] <NICKNAME> was in status
[02/26-19:28] <userlame> ok try this.
[02/26-19:29] <userlame> the first line should be ON 999:TEXT:..spammer*:?:{
[02/26-19:29] <userlame> that should fix it.
[02/26-19:29] <NICKNAME> done
[02/26-19:29] <NICKNAME> try now.
[02/26-19:29] <userlame> k
[02/26-19:30] <userlame> there we go.
[02/26-19:30] <NICKNAME> cool
[02/26-19:30] <NICKNAME> worked fine
[02/26-19:30] <userlame> now u can just change the "add ur kick reason here" to the reason you want put in.
[02/26-19:30] <userlame> and it's set.
[02/26-19:31] <NICKNAME> i did just now.
[02/26-19:31] <userlame> then unban me and we'll call it even. :Ş
[02/26-19:32] <NICKNAME> just did,,
[02/26-19:32] <userlame> hehe thnx.
[02/26-19:34] <NICKNAME> last test
[02/26-19:34] <NICKNAME> make sure changes I made are ok
[02/26-19:34] <userlame> k.
[02/26-19:35] <userlame> a-ok.
[02/26-19:35] <NICKNAME> cool
[02/26-19:35] <NICKNAME> man u know this stuff real well
[02/26-19:36] <NICKNAME> wouldm have taken me ages
[02/26-19:36] <NICKNAME> if at all LOL
[02/26-19:36] <userlame> i've been doing it for 6 yrs now on and off.
[02/26-19:36] <userlame> hehe
[02/26-19:36] <userlame> i'm a nerd.
[02/26-19:36] <userlame> hehe
Session Close: Tue Feb 26 19:52:25 2002

Hopefully someone will find this post of some use (Real post below so google will find it better. Sigh. This will be fixed in the site updates.)

And another post so the spiders don't link to the wrong page. Man, I need to fix this crap.

I had some problems with getting vsftpd up and running on slackware, and I thought I'd document them for all to see. I was able to get it running and connect to it but all logins failed with

I am using userlist_enable=YES, userlist_deny=NO, and userlist_file=/etc/vsftpd.user_list. /etc/vsftpd.user_list contains local users created specifically for ftp purposes. Everything looked to be configured correctly; I could log in to the accounts locally and everything in the vsftpd.conf file looked correct. After much hair-pulling and googling, I found a post here [linuxquestions.org] where someone suggests that they had to use the line

I had the shell of these users set to /bin/false, and adding this line to the config file allowed the users to log in.

I had attempted to change one of the users shells to /bin/sh and tested a login, but it didn't work. I am not sure why, but I don't much care as I don't want these users to have shells anyway. I consider it solved.

I had some problems with getting vsftpd up and running on slackware, and I thought I'd document them for all to see. I was able to get it running and connect to it but all logins failed with

I am using userlist_enable=YES, userlist_deny=NO, and userlist_file=/etc/vsftpd.user_list. /etc/vsftpd.user_list contains local users created specifically for ftp purposes. Everything looked to be configured correctly; I could log in to the accounts locally and everything in the vsftpd.conf file looked correct. After much hair-pulling and googling, I found a post here [linuxquestions.org] where someone suggests that they had to use the line

I had the shell of these users set to /bin/false, and adding this line to the config file allowed the users to log in.

I had attempted to change one of the users shells to /bin/sh and tested a login, but it didn't work. I am not sure why, but I don't much care as I don't want these users to have shells anyway. I consider it solved.

I thought this was funny...

$ grep -R blows /usr/src/linux/*
/usr/src/linux/Documentation/sound/oss/NM256:when it blows up your computer.
/usr/src/linux/arch/cris/arch-v10/mm/init.c: /* Note that nothing blows up just because we do this remapping
/usr/src/linux/arch/i386/kernel/apm.c: { /* APM blows on shutdown */
/usr/src/linux/arch/ppc/platforms/ev64260.h:/* Assembler in bootwrapper blows up if 'max' is used */
/usr/src/linux/arch/ppc/syslib/qspan_pci.c: * This blows......
/usr/src/linux/arch/sparc/kernel/sun4m_irq.c: * 0x0b the system blows (it starts to whistle!).
/usr/src/linux/arch/sparc/mm/srmmu.c: /* anything above 1280 blows up */
/usr/src/linux/drivers/net/wireless/atmel.c: /* this blows chunks. */
/usr/src/linux/drivers/scsi/sgiwd93.c: struct scsi_host_template *SGIblows, int unit, int irq,
/usr/src/linux/drivers/scsi/sgiwd93.c: host = scsi_register(SGIblows, sizeof(struct ip22_hostdata));
/usr/src/linux/drivers/scsi/sgiwd93.c:static int __init sgiwd93_detect(struct scsi_host_template *SGIblows)
/usr/src/linux/drivers/scsi/sgiwd93.c: SGIblows->proc_name = "SGIWD93";
/usr/src/linux/drivers/scsi/sgiwd93.c: sgiwd93_host = sgiwd93_setup_scsi(SGIblows, 0, SGI_WD93_0_IRQ,
/usr/src/linux/drivers/scsi/sgiwd93.c: sgiwd93_host1 = sgiwd93_setup_scsi(SGIblows, 1, SGI_WD93_1_IRQ,
/usr/src/linux/drivers/serial/68360serial.c: * it blows away the port control information.
/usr/src/linux/drivers/serial/cpm_uart/cpm_uart_cpm1.c: /* was hostalloc but changed cause it blows away the */
/usr/src/linux/drivers/usb/mon/mon_stat.c: * Note that this code blows through locks, so make sure that

I thought this was funny...

$ grep -R blows /usr/src/linux/*
/usr/src/linux/Documentation/sound/oss/NM256:when it blows up your computer.
/usr/src/linux/arch/cris/arch-v10/mm/init.c: /* Note that nothing blows up just because we do this remapping
/usr/src/linux/arch/i386/kernel/apm.c: { /* APM blows on shutdown */
/usr/src/linux/arch/ppc/platforms/ev64260.h:/* Assembler in bootwrapper blows up if 'max' is used */
/usr/src/linux/arch/ppc/syslib/qspan_pci.c: * This blows......
/usr/src/linux/arch/sparc/kernel/sun4m_irq.c: * 0x0b the system blows (it starts to whistle!).
/usr/src/linux/arch/sparc/mm/srmmu.c: /* anything above 1280 blows up */
/usr/src/linux/drivers/net/wireless/atmel.c: /* this blows chunks. */
/usr/src/linux/drivers/scsi/sgiwd93.c: struct scsi_host_template *SGIblows, int unit, int irq,
/usr/src/linux/drivers/scsi/sgiwd93.c: host = scsi_register(SGIblows, sizeof(struct ip22_hostdata));
/usr/src/linux/drivers/scsi/sgiwd93.c:static int __init sgiwd93_detect(struct scsi_host_template *SGIblows)
/usr/src/linux/drivers/scsi/sgiwd93.c: SGIblows->proc_name = "SGIWD93";
/usr/src/linux/drivers/scsi/sgiwd93.c: sgiwd93_host = sgiwd93_setup_scsi(SGIblows, 0, SGI_WD93_0_IRQ,
/usr/src/linux/drivers/scsi/sgiwd93.c: sgiwd93_host1 = sgiwd93_setup_scsi(SGIblows, 1, SGI_WD93_1_IRQ,
/usr/src/linux/drivers/serial/68360serial.c: * it blows away the port control information.
/usr/src/linux/drivers/serial/cpm_uart/cpm_uart_cpm1.c: /* was hostalloc but changed cause it blows away the */
/usr/src/linux/drivers/usb/mon/mon_stat.c: * Note that this code blows through locks, so make sure that

I've slopped together a little perl that I'd like to share...it would be useful if you have a Logitech G15 keyboard and g15daemon (linux). Right now it just spits out the output of fortune (you'll want this in your $PATH), but it could be used to filter/scroll any kind of text quite easily. The code is nasty and will be cleaned up. Anyways, it's here [userlame.com]. Enjoy.

I've slopped together a little perl that I'd like to share...it would be useful if you have a Logitech G15 keyboard and g15daemon (linux). Right now it just spits out the output of fortune (you'll want this in your $PATH), but it could be used to filter/scroll any kind of text quite easily. The code is nasty and will be cleaned up. Anyways, it's here [userlame.com]. Enjoy.

I like this guy's point [berylliumsphere.com].

I like this guy's point [berylliumsphere.com].

Can someone please explain this to me?



YOU JUST FOUND 2 DISPLAY DEVICES ALL ON YOUR OWN!

Ok, ok, so I'm an idiot. I kept playing and playing with the config and getting nowhere....and right there in front of my face was this little gem:



just above everything else in the Device section I was monkeying with. Once that line was removed, everything worked as expected again.

Yipes. I learned a lesson the hard way last night. I don't use very long leases (~8 hours), and when I restart my firewall conf scripts (shorewall) dhcpd needs to be restarted as it no longer responds (I need to dig into this further - notes in this thread).

I've been writing a failover daemon to run on both the servers and in doing so, restarted the firewall at one point and did not restart the dhcp daemon. I was working - on those scripts actually - remotely from work, when I was suddenly and rudely disconnected. My jump box resides within a dhcp dmz, and it's lease timed out. When trying to renew it, it got no response and thus lost its address. Had me a bit worried too; I thought the box had caught fire or something.

Yipes. I learned a lesson the hard way last night. I don't use very long leases (~8 hours), and when I restart my firewall conf scripts (shorewall) dhcpd needs to be restarted as it no longer responds (I need to dig into this further - notes in this thread).

I've been writing a failover daemon to run on both the servers and in doing so, restarted the firewall at one point and did not restart the dhcp daemon. I was working - on those scripts actually - remotely from work, when I was suddenly and rudely disconnected. My jump box resides within a dhcp dmz, and it's lease timed out. When trying to renew it, it got no response and thus lost its address. Had me a bit worried too; I thought the box had caught fire or something.

So the power supply got here. Here's a preview:
[Note: images updated]







Details to follow...

So the power supply got here. Here's a preview:
[Note: images updated]







Details to follow...

I think I'll work on an old project.

I think I'll work on an old project.

PASTE:


*** Warm reboot...

Clearing memory
Probing devices
Finding image...
Loading /pc-card:1,\x86\kernel\primary.krn

Starting Press CTRL-C for special boot menu
..................

NetApp Release 7.1: Fri Dec 23 02:32:04 PST 2005
Copyright (c) 1992-2005 Network Appliance, Inc.
Starting boot on Mon Sep 4 03:33:04 GMT 2006
Mon Sep 4 03:33:14 GMT [scsi.cmd.transportError:error]: Device 8.23: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportEr
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.21: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.17: Transport
error during execution of command: HA status 0x9: cdb
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.20: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.22: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:erro
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:15 GMT [scsi.cmd.transportError:error]: Device 8.27: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.23: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.20: Transport
error during execution of command: HA status 0x9: cdb
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.retrySuccess:info]: Device 8.22: request succe
ssful after retry #1: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.29: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.retrySuccess:info]: Device 8.27: request succe
ssful after retry #1: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.18: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.21: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:16 GMT [scsi.cmd.transportError:error]: Device 8.17: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.29: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.23: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:erro
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.21: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.17: Transport
error during execution of command: HA status 0x9: cdb
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.20: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:18 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.18: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]:
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.19: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.21: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.21: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.17: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.17: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.20: Transpo
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.20: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.26: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.29: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.29: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:19 GMT [scsi.cmd.transportError:error]: Device 8.23: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:19 GMT [scsi.cmd.noMorePaths:error]: Device 8.23
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.18 (S/N 3FP0RK0D00002218448V)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.19 (S/N 3FP0HVF200007211BXH6)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warn
er error prevents command from being sent to device) while reading ownership on
disk 8.21 (S/N 3FP0SMZH00002219BRKC)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.17 (S/N 3FP0RDGJ00007217VR6W)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.20 (S/N 3FP0S7NW00002219B4JS)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.26 (S/N 3FP0RJQ5000022184UK5)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.29 (S/N 3FP0SNH300002219H5RW)
Mon Sep 4 03:33:20 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.23 (S/N 3FP0SHL600002219B4JB)
Mon Sep 4 03:33:22 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:22 GMT [scsi.cmd.transportError:error]: Device 8.18: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:23 GMT [scsi.cmd.transportError:error]: Device 8.16: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:23 GMT [scsi.cmd.retrySuccess:info]: Device 8.18: request succe
ssful after retry #1: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:23 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.16: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.21: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.17: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.retrySuccess:info]:
ssful after retry #2: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.25: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.23: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.18: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:24 GMT [scsi.cmd.transportError:error]: Device 8.24: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.16: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.25: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:25 GMT [scsi.cmd.retrySuccess:info]:
ssful after retry #1: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.18: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:25 GMT [scsi.cmd.retrySuccess:info]: Device 8.21: request succe
ssful after retry #1: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.17: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.24: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:25 GMT [scsi.cmd.transportError:erro
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:25 GMT [scsi.cmd.noMorePaths:error]: Device 8.16: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:26 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.16 (S/N 3FP0RET800007217VQZJ)
Mon Sep 4 03:33:27 GMT [scsi.cmd.transportError:error]: Device 8.25: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:27 GMT [scsi.cmd.retrySuccess:info]: Device 8.18: request succe
ssful after retry #2: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:27 GMT [scsi.cmd.transportError:error]: Device 8.19: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:27 GMT [scsi.cmd.retrySuccess:info]: Device 8.17: request succe
ssful after retry #2: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:27 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:27 GMT [scsi.cmd.transportError:error]: Device 8.24: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:28 GMT [scsi.cmd.transportError:error]: Device 8.16: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:28 GMT [scsi.cmd.transportError:erro
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:28 GMT [scsi.cmd.noMorePaths:error]: Device 8.25: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:28 GMT [scsi.cmd.retrySuccess:info]: Device 8.19: request succe
ssful after retry #3: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:28 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:28 GMT [scsi.cmd.transportError:error]: Device 8.24: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3e8:0018.
Mon Sep 4 03:33:28 GMT [scsi.cmd.noMorePaths:error]: Device 8.24: No more paths
to device: cdb 0x28:0000a3e8:0018. All retries have failed.
Mon Sep 4 03:33:29 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.25 (S/N 3CD1P3EC00002132B8EM)
Mon Sep 4 03:33:29 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapt
er error prevents command from being sent to device) while reading ownership on
disk 8.24 (S/N 3CD1E6X30000212429MS)
Mon Sep 4 03:33:30 GMT [scsi.cmd.transportError:error]: Device 8.16: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:30 GMT [scsi.cmd.transportError:error]: Device 8.26: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f8:0008.
Mon Sep 4 03:33:30 GMT [scsi.cmd.noMorePaths:error]: Device 8.26: No more paths
to device: cdb 0x28:0000a3f8:0008. All retries have failed.
Mon Sep 4 03:33:30 GMT [diskown.errorDuringIO:error]: error 23 (adapter error p
revents command from being sent to device) on disk 8.26 (S/N 3FP0RJQ5000022184UK
5) while reading individual disk ownership area
Mon Sep 4 03:33:30 GMT [scsi.cmd.transportError:error]: Device 8.25: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:30 GMT [scsi.cmd.transportError:error]: Device 8.16: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:31 GMT [scsi.cmd.transportError:error]: Device 8.25: Transport
error during execution of command: HA status 0x9: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:31 GMT [scsi.cmd.retrySuccess:info]: Device 8.25: request succe
ssful after retry #2: cdb 0x28:0000a3f0:0008.
Mon Sep 4 03:33:31 GMT [scsi.cmd.retrySuccess:info]: Device 8.16: request succe
ssful after retry #3: cdb 0x28:0000a3f0:0008.
No disks were detected on Fibre Channel port A
Rebooting... (ctrl-c to break reboot loop)
[LCinfo] Rebooting: No local disks.

*** Warm reboot...

Clearing memory
Probing devices
Finding image...
Loading /pc-card:1,\x86\kernel\primary.krn

nap01> ifconfig e5a
e5a: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:04:23:b2:4a:56 (auto-unknown-cfg_down) flowcontrol full
nap01> ping 10.8.196.4
ping: wrote 10.8.196.4 64 chars, error=No route to host
ping: wrote 10.8.196.4 64 chars, error=No route to host
nap01> ifconfig e5a 10.8.196.31
nap01> Sun Sep 3 22:41:28 CDT [10/100/1000-VI/e5a:info]: Ethernet e5a: Link up

nap01> ping 10.8.196.4
10.8.196.4 is alive
nap01> ifconfig -a
e0: flags=1108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:a0:98:01:4c:bc (auto-unknown-cfg_down) flowcontrol full
e5a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 10.8.196.31 netmask 0xff000000 broadcast 10.255.255.255
ether 00:04:23:b2:4a:56 (auto-1000t-fd-up) flowcontrol full
e5b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:04:23:b2:4a:57 (auto-unknown-cfg_down) flowcontrol full
lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
ether 00:00:00:00:00:00 (VIA Provider)
nap01> route -sn
Routing tables

Internet:
Destination Gateway Flags Refs Use Interface
10 link#2 UC 0 0 e5a
10.8.196.4 0:3:ba:69:4:c8 UHL 1 1 e5a
127 127.0.0.1 UGS 0 0 lo
127.0.0.1 127.0.0.1 UH 1 0 lo
nap01>

I was reading an interview [blogs.zdnet.com] that was posted on slashdot today with the lead engineer of the linux flash player. I was quite pleased with this little gem:



Now personally, I despise having to look at flash at all, but I do enjoy a good humorous video (hey, there's one on this site!) which is usually in flash. YouTube, google video, all flash. This has been so annoying for so long, and no amount of tweaking OSS emulation seemed to help. Reading this makes the userlame pleased.

I was reading an interview [blogs.zdnet.com] that was posted on slashdot today with the lead engineer of the linux flash player. I was quite pleased with this little gem:



Now personally, I despise having to look at flash at all, but I do enjoy a good humorous video (hey, there's one on this site!) which is usually in flash. YouTube, google video, all flash. This has been so annoying for so long, and no amount of tweaking OSS emulation seemed to help. Reading this makes the userlame pleased.

A story
By: userlame
©2006 userlame.com All rights reserved to everyone

Today, I was peacefully sleeping, as I am wont to do, when an important lesson was heaped upon me. As I lay in my bed, dreaming my happy dreams, a horrific tragedy was brewing not 10 feet from my listless self.

About 1:10 P.M. CST I was awoken by the sound of a loud *POP* and my kitty [userlame.com] flew from his post asleep by my side. Across my stomach he ran, eliciting a guttural "ugh" from deep within. I sprang from my slumber with a brief photogene of light dancing across my eyes.

"wtf?!," I said as I began to panic. "Did the power just surge?" It was raining outside, and I have two fans in my windows running pretty much constantly to keep this datacenter I call a bedroom cool. Could water have leaked in causing a short?

Around my room I ran, seeking out the cause of this disturbance. Nothing that I could find seemed to coincide with what I had heard or believed I had seen. The only evidence I had that anything had happened was the fact that my desktop had mysteriously powered off.

I dug deeper and deeper and still found nothing. I moved the aforementinoed fans, turned them off, checked for water, and still nothing. Satisfied that nothing was currently shorting, or going to explode, I attempted to power the desktop back on. Nothing. I clicked the power supply off and back on again, and still nothing. "Oh shit," I thought to myself, "everything else plugged in to the same power strip is still on. Nothing else has been affected save my desktop." Finding no other causes I decided to make sure the thing was still plugged in. Not that I saw how it could be otherwise, but I had gone through all other things I could find.

So under my desk I went searching for the power cord trailed from the desktop machine. And there, dear friends, is where I found the moral of this little tale. And the moral is this:

DON'T USE CHEAP POWER CABLES.



This cable was just a cheap little number that had been provided with the cheap little power supply that came with my case. And somehow, evidently, the cable had acquired a short inside that picked this very moment to fry. Note also that the cable had not moved, nor was there any other environmental cause for this failure to occur at this time. Random happenstance, it seems.

There is a happy ending to the story, however. I replaced the power cable and my desktop has been once again brought to life. Phew.

So let me reiterate in case you missed it the first time:

DON'T USE CHEAP POWER CABLES.

Thank you, and good night.

A story
By: userlame
©2006 userlame.com All rights reserved to everyone

Today, I was peacefully sleeping, as I am wont to do, when an important lesson was heaped upon me. As I lay in my bed, dreaming my happy dreams, a horrific tragedy was brewing not 10 feet from my listless self.

About 1:10 P.M. CST I was awoken by the sound of a loud *POP* and my kitty [userlame.com] flew from his post asleep by my side. Across my stomach he ran, eliciting a guttural "ugh" from deep within. I sprang from my slumber with a brief photogene of light dancing across my eyes.

"wtf?!," I said as I began to panic. "Did the power just surge?" It was raining outside, and I have two fans in my windows running pretty much constantly to keep this datacenter I call a bedroom cool. Could water have leaked in causing a short?

Around my room I ran, seeking out the cause of this disturbance. Nothing that I could find seemed to coincide with what I had heard or believed I had seen. The only evidence I had that anything had happened was the fact that my desktop had mysteriously powered off.

I dug deeper and deeper and still found nothing. I moved the aforementinoed fans, turned them off, checked for water, and still nothing. Satisfied that nothing was currently shorting, or going to explode, I attempted to power the desktop back on. Nothing. I clicked the power supply off and back on again, and still nothing. "Oh shit," I thought to myself, "everything else plugged in to the same power strip is still on. Nothing else has been affected save my desktop." Finding no other causes I decided to make sure the thing was still plugged in. Not that I saw how it could be otherwise, but I had gone through all other things I could find.

So under my desk I went searching for the power cord trailed from the desktop machine. And there, dear friends, is where I found the moral of this little tale. And the moral is this:

DON'T USE CHEAP POWER CABLES.



This cable was just a cheap little number that had been provided with the cheap little power supply that came with my case. And somehow, evidently, the cable had acquired a short inside that picked this very moment to fry. Note also that the cable had not moved, nor was there any other environmental cause for this failure to occur at this time. Random happenstance, it seems.

There is a happy ending to the story, however. I replaced the power cable and my desktop has been once again brought to life. Phew.

So let me reiterate in case you missed it the first time:

DON'T USE CHEAP POWER CABLES.

Thank you, and good night.