When running a local area network, one of the goals is usually to provide an environment to the users that make the network transparent. An important step for this is to keep vital data such as user account information (e.g. /etc/hosts, /etc/passwd and /etc/group files) synchronized between all hosts. For host name resolution, a powerful and sophisticated service - DNS exists. For other tasks, there is no such specialized service. Moreover, if you manage only a small closed intranet without Internet connectivity, setting up DNS may not seem worth the trouble for many administrators.

To be able to use the functionality of a module which was built as a DSO you have to place corresponding 'LoadModule' lines at this location so the directives contained in it are actually available before they are used. Please read the file README.DSO in the Apache 1.3 distribution for more details about the DSO mechanism and run 'httpd -l' for the list of already built-in (statically linked and thus always available) modules in your httpd binary.

Basically for communication where there is a client-server flavor, the server process creates a socket and the client socket accesses the server through client socket techniques.

Socket

A socket is fundamentally nothing but an end point of communication. It can be of two types: Physical socket and Logical socket. In Logical socket operating system has its system calls, which creates them. Now for client-server access the socket needs three things to provide service or ask for service.

This article is basically written for Rsync, a very fast, flexible and robust backup utility. We will look at how you can utilize and configure this program to take the daily backup from your production servers.

So now that you have installed FreeBSD, what do you do next? Well there are lots of things you can configure. Here, we bring you an article that focuses on various aspects like environment, shells, etc, which need configuration. This should set the ball rolling.