OpenVOS Blog

The STCP services file is misunderstood by many people; you cannot use it to reserve port numbers. This blog explains what the file is for and how to resolve port conflicts.

Sometimes netstat will show a socket that appears to be stuck. The remote application has been terminated, sometimes even the OpenVOS application has been terminated but netstat is still showing the socket. This article will explain why this happens and what you can do about it.

Something that people moving from TCP_OS to STCP notice right off the bat is that the set of TCP statistics displayed by the TCP_OS netstat command is quite a bit richer than that displayed by STCP. I provide a macro to make the output even more useful.

When system log messages (all of them: hardware, security, syserr, etc) are generated in OpenVOS, they are sent to the syserr partition, and an event is notified. A process named TheOverseer is waiting on that event, along with a lot of other events.

Are you still working on VOS using a 80 column by 24 line view?  Get with the flow and see the big picture.

When people think of IPsec they think of data encryption but it can also be used to drop packets or allow them without any encryption. It can do this based on the source and destination IP address and port numbers. Which is exactly what a firewall does; so you can use the IPsec feature of VOS as a firewall.

"Dot" pathnames can really shorten the amount of typing you must do for some common commands. Here’s how you can use them.

Based on the questions I have seen over the last few month,s the process of setting up and using an SSH tunnel is not well understood. Here is my attempt to explain it.

We adopted the name OpenVOS to emphasize some new capabilities, and to ensure that our VOS (now, OpenVOS) customers took full advantage of them.

Lately, I've been porting several new open-source packages to OpenVOS 17.0. I nearly missed an error that would occur in 2038.