I’m pretty happy with [...]]]> Well, I’ve finally deployed some production Openfiler ESA 2.99.1 machines as home-brew iSCSI boxes, primarily used for backups or low-stress virtual storage. Yes, they’re great — my basic write speeds on a Core 2 Duo box (recycled Dell Precision 390 workstation with 2GB of RAM and a single 1TB drive *no* RAID):

administrator@mail:/backup-iscsi$ sudo dd if=/dev/zero of=garbage bs=131072 count=20000
20000+0 records in
20000+0 records out
2621440000 bytes (2.6 GB) copied, 40.8493 s, 64.2 MB/s

I’m pretty happy with that. What I’m not please with is a 56MB log (/var/log/secure) filled with strange messages:

Jul 26 12:25:46 e0-002 sudo: openfiler : TTY=unknown ; PWD=/opt/openfiler/var/www/htdocs ; USER=root ; COMMAND=/usr/bin/uptime
Jul 26 12:25:46 e0-002 sudo: PAM unable to dlopen(/lib64/security/pam_gnome_keyring.so)
Jul 26 12:25:46 e0-002 sudo: PAM [error: /lib64/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory]
Jul 26 12:25:46 e0-002 sudo: PAM adding faulty module: /lib64/security/pam_gnome_keyring.so

Okay, so the first message isn’t strange. In fact, it’s normal. But I couldn’t figure out why a non-GUI (yes, it has a web interface, but no default window manager) distro was trying to load the Gnome keyring shared object. I still don’t know why. What I do know is how to get rid of this message:

1. Verify which PAM files reference this shared object:

1. [root@e0-002 pam.d]# cd /etc/pam.d/
   [root@e0-002 pam.d]# grep -i -n 'pam_gnome_keyring.so' *
   system-auth:5:# FL: Have (patched) pam_gnome_keyring.so grab the password before pam_unix.so
   system-auth:6:auth        optional      pam_gnome_keyring.so
   system-auth:16:password    optional      pam_gnome_keyring.so

2. In this instance, the ‘system-auth’ file contained these troublesome pam_gnome_keyring.so entries.
3. Fire-up your favorite text editor and comment those lines.
4. Reboot & enjoy a log without an absurd amount of irrelevant errors.

As a result of my frugality, I got my hands on an Adtran Atlas 550 to be used for partitioning a single PRI into two PRIs at my workplace. In addition to the partitioning, this system provides the added bonus of dynamic number substitution. What’s this mean for me? Substituting costly 411 directory service [...]]]>

As a result of my frugality, I got my hands on an Adtran Atlas 550 to be used for partitioning a single PRI into two PRIs at my workplace. In addition to the partitioning, this system provides the added bonus of dynamic number substitution. What’s this mean for me? Substituting costly 411 directory service for free Goog-411 service (which I prefer over traditional 411). I’m also able to create a number rejection list to block those NSFW 900* calls [or variation thereof], but the number substitution templates seem much more interesting…

How to do it:

• Telnet to yohost.yodomain and log-in
• Dial Plan > Network Term > Interface # (1 in my case) > Enter
• Select Substitution Template
• Enter the Original DNIS number (the phone number originally dialed)
• Enter the Substitution DNIS number (the phone number you’d like to dial)
• Go back to the main menu and log-out

Remember, this change is transparent (and instant — no need to write/commit the config to startup), so the next time callers decide to hit up the 411 directory service, their call should be automagically routed to 1-800-goog411 (1-800-4664411). Since we’re a fairly small office I don’t think this number substituion presents a problem with Googles Terms of Service, but if you’re considering this change on a massive scale  I’d consider reading over Google’s TOS agreement (particularly section 5.3).