Saturday, January 31, 2009

Looks like Google is having issues this morning. Any search result I click on, with the exception of a Google-hosted site, is issuing a malware warning. Let's see how long it takes to resolve. The issue started for me at 9:34AM EST:

Wednesday, January 28, 2009

Syslog on Solaris 10 - Remote Loghosts

Just a quick note here to help others that may run into the same issue. I have had a Solaris 10 FTP server running for several years. I have grossly neglected it and only recently decided to give it any attention whatsoever.

I wanted to have the server send syslog messages to a remote loghost. Normally, this is very simple. I would just add a line in /etc/hosts to define the remote loghost, and then add a line in /etc/syslog.conf to tell syslogd which events to send to the loghost.

My problem was that syslogd kept determining that the local system was "loghost", and not the server that I defined in /etc/hosts. I could verify this by killing the syslogd process and then running it manually with the "-d" parameter.

It turns out that there was another entry on the system, defining the localhost as "loghost" in the file /etc/inet/ipnodes.

I simply removed the line altogether, restarted syslogd and voila! The remote loghost started receiving messages from my estranged FTP server.

Tuesday, January 27, 2009


Bah! Why does Sun Microsystems force the Solaris community to log into a website to download patches and patch clusters? Why can't they just have an FTP site we can get the updates from?

I constantly have problems with the sunsolve site; It's frequently slow as hell, and just throws error messages at me all the time. Today, I can't even get a patch cluster:
Meh. I know this is an unproductive post, but no one else I know will care about this problem. Maybe one of the billions out there on the Internet will feel my pain.

Update- Apparently, I'm not alone afterall:
http://ptribble.blogspot.com/2007/08/sunsolve-needs-makeover.html