I was working on a recently built Solaris 9 server with a fresh copy of MQ installed.
During application testing, we were getting 2195 errors from our application when establishing more than 3 concurrent connects to MQ.
After a day of wasted de-bugging of our application, we put it down to the system, and it seems we may have been correct. There is an install chapter in the MQ V6.0 documentation that should NOT be overlooked.
Category: unix
Just when I had gone and written my own init scripts for MQ, IBM release a support pack for Linux/Redhat. It is in RPM (rpm2cpio.pl anyone?) format, and seems very linuxy. I’ll stick with my own Solaris scripts, but should you run MQ on linux, then check it out.
I’m so used to making branches in CVS.
<br /> cvs tag -b system_test<br /> As the CVS doco states simply, “This splits off a branch based on the current revisions in the working copy”, and these revisions will get assigned the branch name, in this case `system_test’. Simple, powerful enough and quick!
But Rational Clearcase is a different beast as I learn it. You have to make your branchtype.
I know it has been blogged to death by now, but Mac OSX, my desktop OS of choice, is now officially a standard UNIX. Specifically to the UNIX 03 Product Standard. This confirms it conforms to Version 3 of the Single UNIX Specification. This makes Apple Inc. an official UNIX vendor along with all the other big boys.
On the serverside, I will stick with OpenBSD as my personal server OS of choice, with Solaris following close behind.
A quick lesson (for my own benefit as much as yours) in applying Access Control Lists (ACL) on files and directories under Solaris (in this case Solaris 9).
To allow group “somegroup” read only access to a folder recursively, you need to set the ACL on EVERY directory and file. This is due to the fact that the Solaris setfacl command does not have a recursive option (do not confuse -r with recurse).
Was implementing an MQ cluster at work recently, and the question arose on setting up init scripts for MQ, specifically the listener, runmqlsr. I was advised that inetd is the usual method for setting up any MQ daemon.
However, I read a blog post on A Hursley view on MQ blog, and it stated that launching the runmqlsr seperately, and not using inetd is the now preferred method of having your MQ daemon running.
I recently starting using Clearcase for versioning, at work. I come from a CVS background, so initially found it to be cumbersome. For example, here is how i added a file to the repository:
CVS method:
<br /> <a href="http://search.twitter.com/search?q=%23" class="tweet-hashtag">#</a> Change to your already checked out working folder<br /> cd /your/working/dir<br /> <a href="http://search.twitter.com/search?q=%23" class="tweet-hashtag">#</a> list folder contents, will see checked out working files<br /> ls -l<br /> <a href="http://search.
I’m finally in a job where I can get to use Solaris close to 100% of the time. Goodbye, Au Revoir, Arrivederci Windows 2003 Server. Hello, Bonjour, Ciao lovely UNIX!.
Oh yeah so I started a new job with CGI today. Technical Architect. Very business sounding, but a good role!