Lil’ bit: Threading problem on Solaris with GCC

2008/05/23 23:31:00
Print Friendly

After much confusion and heartache, some google searching indicates to me that there is a problem on Solaris using threads with gcc. When applications compiled with gcc attempt to throw exceptions from within threads sometimes they do not get caught, and hence the application terminates with the message:

terminate called recursively

Ref:
http://gcc.gnu.org/ml/gcc-bugs/2007-06/msg01137.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32344

The current workaround for my project was to forgo threads, but one of the developers came up with the idea to link in the Solaris libc++ to avoid this problem.

AHA! It works!

2007/08/17 00:02:00
Print Friendly

As usual, when I have some time off, I tinker with my network and tend to break something.

I decided that I could let my wireless router rest a bit by turning off its gateway functionality, thereby accepting it into my LAN and telling it not to treat the other side like the wilds of the Internet. This means it wasn’t translating addresses for me anymore. No NAT.

This is all well and good, but now the network on the other side of that wireless router needs to be known to my central Linux router. Hmmm!

So, I typed in

sudo /<span>sbin</span>/ip route add 172.30.19.0/30 via 172.30.100.2 dev eth2

where 172.30.19.0 is the wireless network and 172.30.100.0 is the tiny (2 connection) network between the Linux router and the wireless router.

This made things work great, but I wondered how to ensure that this route was added at each reboot.

In CentOS 3, this information is stored in the /etc/sysconfig/static-routes file like so:

any net 172.30.19.0 netmask 255.255.255.252 gw 172.30.100.2 dev eth2

This syntax is used by the

/sbin/route

command.

Well, off to bed.

Life is returning to normal?

2007/07/10 14:25:00
Print Friendly

Where’s the fun in normal?

I’m home sick today. Another doctor’s visit. If anyone wants to know, I’ll email you with what’s up. Thank you all for your support during this painful time.

The ladyfriend and I went to Baltimore where we checked out the aquarium. Pics are here. You should check them out. I’m getting better.

I’m not going to make it to Otakon this year. She’s taking me to a Dave Matthews concert and I don’t know if I can afford this much traveling. Sorry folks.

On the home front, Koneko has moved out. I’m sad now. She’s not around. Even though she didn’t do much with me while she was here, at least the company was nice. I’ve got the freedom to cook naked (like Joey on Friends), but I can’t help but want to bug someone occasionally. The cats are only marginally interesting.

I’m glad I’ve got a new friend to bring over and bug. B)

On the other hand, I can finally get down to business with some things I want to do to the house with impunity. Also, it’s nice to be able to browse porn^W^W enjoy some alone time.

Next week is CISSP training. The test promises to be quite difficult and I’m not sure if I’m up for this, but we’ll give it a shot. I should really review the books before the class!

Speaking of books, I’m still making my way through my Ruby on Rails book. Eventually my plan is to redo this entire site in rails, giving me the control I want. I have to say, though, b2evolution and gallery have been meeting my needs quite nicely.

I haven’t talked to Sigje lately and think I should give her an email/call/etc.

Oh, and the solution for Spamassassin didn’t work. I’ve put the following into my local.cf file:

trusted_networks 72.36.174.35 127.0.0.1

Wish me luck. Hopefully this will force it to just accept anything from itself without checking it. The fact that SPAM URLs were in the log emails was tripping it, but then again, these SPAM URLs are what the log emails are reporting. Sheesh. This wasn’t an issue on the previous version of CentOS.

I really miss my girlfriend. I really need to ask her what name to give her on the blog. I could pick, but I don’t want to be mean.

Logwatch and Spamassassin

2007/06/27 09:32:00
Print Friendly

Yesterday I realized that I hadn’t been getting any emails from my web/mail server. It was quite odd.

Looking in my SPAM folder I found all of the system emails that had been tagged and sent there. Every once in a while some legitimate (“HAM”) gets marked as SPAM and put in there.

I wasn’t expecting Logwatch emails to be easily marked as SPAM.

So, I checked out why it was listing them as such, and it led me to this line:

X-Spam-Status: Yes, score=6.4 required=5.0tests=ALL_TRUSTED,URIBL_BLACK,URIBL_JP_SURBL,URIBL_OB_SURBL,WHOIS_DMNBYPROXY,WHOIS_PRIVACYPOST autolearn=no version=3.2.1

As the Logwatch file reports on SPAM and associated information, I can see why it might have tripped the URI Black Lists (URIBL) and maybe the WHOIS rules, but it still didn’t make sense to me.

Usually if something is marked ALL_TRUSTED, no further checking is done, but I realize that in CentOS-5, this no longer appears to be the case. You are expected to set it up.

So, I edited /usr/share/spamassassin/60_shortcircuit.cf and uncommented the following line:

# if you have taken the time to correctly specify your "trusted_networks",# this is another good way to save CPUshortcircuit ALL_TRUSTED on

I think this should work.

Annoyance with SELinux

2007/05/29 14:26:00
Print Friendly

If you don’t know what SELinux is, start here.

I just spent the last hour or two trying to figure out why syslog would not log anything on one of my machines. It turns out I must’ve copied an updated /etc/services file from /tmp to /etc. This would normally be fine, but the file did not contain the correct context. Instead, copying it gave it the context of the /tmp directory.

Hence, syslog would not start. Because syslog is where SELinux logs its errors, I couldn’t see any errors to lead me to figure out what the problem was.

Once I changed SELinux from enforcing to permissive with:

/usr/sbin/setenforcing Permissive

I could see that syslog started fine and was telling me that the context on /etc/services was out of wack.

Ergh…

I wonder if there is some way I can make sure this doesn’t happen again?

I guess I could use the setfiles command frequently to ensure that all of the file contexts are set correctly.

Sheesh.

How was your day? :-)