Sample interfaces files for multiple network handlers

The following example shows an interfaces file for an Adaptive Server with two network interfaces, each connected to a different network. The server host machine’s network address is 131.214.1.246 on Network 1 and 131.214.1.247 on Network 2.

# PRODUCTION server with two network listeners
 PRODUCTION<tab>3<tab>3<newline>
 <tab>master tli tcp /dev/tcp \x0002130a83d601f60000000000000000
 <tab>master tli tcp /dev/tcp \x0002130a83d601f70000000000000000
 <tab>query tli tcp /dev/tcp \x0002130a83d601f60000000000000000

The following example shows an interfaces file for an Adaptive Server with two network interfaces, each connected to a different network. The server host machine is connected to a TCP/IP network, on which it is called SERV_CORPNET, and a DECnet network, on which it is called SERV_ENGNET.

# PRODUCTION server with two network listeners
 PRODUCTION<tab>3<tab>3<newline>
 <tab>master tcp ether SERV_CORPNET 6464
 <tab>master decnet ether SERV_ENGNET 150
 <tab>query tcp ether zeppo 6464

The following example shows an interfaces file for an Adaptive Server with two network interfaces. The server host machine is known as SERV_CORPNET on the corporate network and SERV_ENGNET on the engineering network.

# PRODUCTION server with two network listeners
 PRODUCTION<tab>3<tab>3<newline>
 <tab>master tcp ether SERV_CORPNET 4559
 <tab>master tcp ether SERV_ENGNET 5479
 <tab>query tcp ether SERV_CORPNET 4559

The next time Adaptive Server is restarted, it spawns a network handler process for each master line in the entry that corresponds to the server’s DSLISTEN value. Connections made on each interface will be handled equally, as peers.