Do you use MQ? do you have performance problems when using persistence? An interesting article on understanding this on a Solaris platform. Koops has always been an informative source on getting my MQ performance under check, and again he comes to the front of the pack on analysis of performance issues. read more | digg story

The MQ command level is an integer used by MQ clients that identify what version the WebSphere MQ servers is running. This in conjunction with the Platform attribute allows a client know what commands the MQ server supports. Both are required attributes to determine usable commands. You may be asked by someone what command level your system supports. In the case of MQ V6.0 on Solaris, the following is true:

So many people have written long and excellent examples of an internet application layer filtering solution. However, what if you need a quick and simple internet filtering solution? Want to block out all the garbage for the younger generation? Look no further than Dansguardian. I’ll assume you love OpenBSD as well, and have the following in place: OpenBSD running as your router, multi-homed the same machine running pf the same machine with squid installed and working as a transparent proxy Packet filtering is online, your internet access works from the router and from an internal host with your squid working transparently wget installed Download the latest beta from dansguardian.

Jonathan Schwartz the SUN CTO detailed on his blog about the new deal between Sun and IBM that allows IBM to offer Solaris x86 as a supported OS on their hardware. What does this mean for sysadmins around the world? More Solaris. That’s OK in my books. The less windows servers the better. Someone should tell IBM about their new interest.

A friend was trying to compile cvsgraph on his Mac (10.4.10 intel) the other day and was receiving the error <br /> configure: error: C compiler cannot create executables<br /> By chance he also tried installing a Fink package by source that day as well, and received the same error. We checked out the GCC version <br /> gcc -v<br /> and it showed GCC 3.3. Some google time later, and it turns out this is an older GCC for the current XCode SDK he has installed.

Recently I posted about our Websphere MQ MQCONN 2195 errors, and how we needed to apply the minimal recommended Solaris Kernel tuning for Websphere MQ. Well, we applied the changes, rebooted and connection problems were gone. Our application was able to spawn multiple connections to MQ without the errors we were seeing before. However, we were still getting climbing response times when doing load tests between a request message being sent and a reply message arriving back.

On linux and other [Unix like operating systems][1], you can untar a tar file with an absolute path to a different location. On Solaris using tar you can not. How do you get around this? [Perderabo on the Unix for Advanced and Expert Users forum][2] describes how. Here is an example (names and servers changed to protect the innocent):

I was wondering how to set permissions on an element in clearcase under unix. You can’t just use your normal chmod. After reading “Phil for Humanity” I had the answer: cleartool protect -chmod 550 myscript.sh Quite simple after all. Your file, in this case myscript.sh, will now have the permissions you want. Remember however, if you try to set write permissions on a file element, it wont set. The clearcase man page for protect advises that write perms are ignored – instead to obtain write permission to a file element, it must be checked out.

In Solaris (and UNIX), a process is a zombie, as shown by the message defunct in the ps report. A zombie process is one that has had all its resources freed, but has not received an acknowledgement from a parent process, receipt of which would ordinarily remove its entry from the process table. The next time a system is booted, zombie processes are cleared. Zombies should not affect system performance, and you should not need to remove them.

Following up from the last post, you may be interested in a little reading on Sun’s explanation of the semaphore and shared memory settings for Solaris Kernel parameters, using /etc/system. set semsys:* is for System V Semaphores set shmsys:* is for System V Shared Memory set msgsys:* is for System V Message Queues My personal server OS of choice is OpenBSD, so if you know OpenBSD, then think /etc/sysctl.conf as it is similar.