Archive for February, 2011

Flushing the STCP ARP cache

February 28, 2011

The ARP cache exists in one form or another on every host that communicates via IP over Ethernet. The cache holds the mapping between IP address and Ethernet Media Access Control (MAC) address. If you change an Ethernet adapter on a host named SERVER-1 or replace SERVER-1 with newer / faster hardware all the hosts [...]

Tags: , , ,
Posted in Uncategorized Comments Off

Best Practices for Configuring ftScalable Storage Arrays on OpenVOS Systems

February 22, 2011

This is an updated version of an article that was first posted on November 16, 2010. This version adds several diagrams and covers some additional subtopics.

The ftScalable Storage and ftScalable Storage G2 arrays are highly flexible, scalable hardware storage subsystems. Understanding the benefits and pitfalls of the various RAID types and configuration options, especially how they interact with the OpenVOS operating system, allows you to create an optimal disk topology. While this post is aimed at VOS customers, most of the information is applicable to all operating systems.

Tags: , , ,
Posted in Uncategorized Comments Off

What separates the great programmers from the merely good programmers?

February 21, 2011

I started thinking about the qualities that separate great programmers from merely good programmers. Read on to learn my views.

Tags: , , , , ,
Posted in Uncategorized 1 Comment »

Ports of cflow and cscope are available!

February 17, 2011

I’ve just uploaded ports of cflow and cscope to the VOS anonymous FTP site. Read on for details.

Tags: , , ,
Posted in Uncategorized Comments Off

How do you find out if a new release is faster?

February 17, 2011

So, you are thinking of upgrading to a new release of OpenVOS, or to a newer hardware platform, and you want to know the effect on the response time or the throughput of your application? What do you do to answer this question? Read on to hear some suggestions.

Tags: , , , , ,
Posted in Uncategorized Comments Off

//pardot tracking code