Back in May of 2009 I wrote about securing telnetd so that only the RSN process has the ability to use it (Telnet can’t live with it, can’t live without it).
Your application just detected a critical condition, you can write a message to an application log or even the syserr_log but how do you notify someone right now that the application needs attention?
A common misconception is that TCP guarantees delivery of the data.
The other day I came across a program that allowed me to select from a prepackaged set of queries and then communicated with a server to retrieve the answer to the selected query.
Having the correct time on your module is critical for all kinds of activities including log synchronization and security certificate validation.
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.
I’ve just uploaded ports of cflow and cscope to the VOS anonymous FTP site. Read on for details.
I started thinking about the qualities that separate great programmers from merely good programmers. Read on to learn my views.
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.
I have recently ported several new or updated open-source packages to OpenVOS Release 17.0.