This chapter describes the commands you can run from the SERVER-CONFIG command line. SERVER-CONFIG lets you examine, modify, and save configuration files for MultiNet services.
To invoke SERVER-CONFIG:
$ MULTINET CONFIGURE /SERVERS
SERVER-CONFIG commands affect the configuration of the currently selected service. You can select services with the SELECT command. By default, no service is selected.
At any SERVER-CONFIG prompt, type ? to list the available commands. Use the SERVER-CONFIG HELP command to view online help for each SERVER-CONFIG command.
Changes do not take effect until you do one of the following:
· Reload and restart the MultiNet server process with the MULTINET NETCONTROL command.
· Restart your system.
For details on configuring MultiNet services, refer to the MultiNet Installation and Administrator’s Guide.
The below table lists the commands you can run from the SERVER-CONFIG prompt.
SERVER-CONFIG Command |
Description |
ADD |
Adds a service to the current configuration. |
ATTACH |
Switches terminal control to another process. |
COPY |
Copies a service entry to the current configuration. |
DELETE |
Deletes a service from the current configuration. |
DISABLE |
Disables a service in the current configuration. |
ENABLE |
Enables a service in the current configuration. |
EXIT |
Exits from the SERVER-CONFIG session. |
GET |
Reads a server configuration file; same as GET. |
HELP |
Displays command information. |
NETCONTROL |
Contacts the NETCONTROL server at another site. |
PUSH |
Accesses the DCL command line while pausing SERVER-CONFIG. |
QUIT |
Exits SERVER-CONFIG and prompts to save changes. |
RESTART |
Restarts the master server process. |
SAVE |
Writes out the current server configuration file. |
SELECT |
Selects a server for SET commands. |
SET ACCEPT-HOSTS |
Specifies which hosts can access the server. |
SET ACCEPT-NETS |
Specifies which networks can access the server. |
SET BACKLOG |
Specifies the server connection queue limits. |
SET CONNECTED |
Specifies the connection-request-received routine. |
SET DISABLED-NODES |
Specifies which VMScluster nodes cannot execute the service. |
SET ENABLED-NODES |
Specifies which VMScluster nodes can execute the service. |
SET FLAGS |
Specifies the flag bit mask for service operation control. |
SET INIT |
Specifies the initialize-service routine. |
SET KEEPALIVE-TIMERS |
Sets keep alive timers for a service. |
SET LISTEN |
Specifies the listen-for-connections routine. |
SET LOG-ACCEPTS |
Enables/disables successful connections logging. |
SET LOG-FILE |
Specifies the log message destination. |
SET LOG-REJECTS |
Enables/disables failed connections logging. |
SET MAX-SERVERS |
Specifies the service process limit. |
SET PARAMETERS |
Specifies service-dependent parameters. |
SET PRIORITY |
Specifies a VMS priority for the created processes. |
SET PROCESS |
Specifies that the service is to run in an auxiliary master server process rather than in the main master server process. |
SET PROGRAM |
Specifies a VMS file name for run or merged images. |
SET REJECT-BY-DEFAULT |
Enables/disables conditional connection rejection. |
SET RECEIVE-BUFFER-SPACE |
Specifies the size of the receive socket buffers. |
SET REJECT-HOSTS |
Specifies which hosts are not allowed service access. |
SET REJECT-MESSAGE |
Specifies a rejected connection message. |
SET REJECT-NETS |
Specifies which networks are not allowed service access. |
SET SEND-BUFFER-SPACE |
Specifies the size of the send socket buffers. |
SET SERVICE |
Specifies the perform-service routine. |
SET SERVICE-NAME |
Changes the service name. |
SET SERVICE-TYPE |
Sets the service type advertised for a particular service. |
SET SOCKET-FAMILY |
Specifies the service family address. |
SET SOCKET-OPTIONS |
Specifies the setsockopt() options. |
SET SOCKET-PORT |
Specifies the port for connection listening. |
SET SOCKET-TYPE |
Specifies the socket type. |
SET USERNAME |
Specifies the user name under which the selected service is started. |
SET WORKING-SET-EXTENT |
Specifies how much memory the process will be allowed to use if there are free pages available. |
SET WORKING-SET-QUOTA |
Specifies the maximum amount of memory the process can lock into its working set. |
SHOW |
Shows the current server configuration. |
SHUTDOWN |
Stops the master server process. |
SPAWN |
Invokes the DCL command or creates a subprocess. |
STATUS |
Shows the SERVER-CONFIG service status. |
USE |
Reads a server configuration file; same as GET. |
VERSION |
Shows the SERVER-CONFIG version. |
WRITE |
Writes the current server configuration; same as SAVE. |
Adds a new service to the current server configuration and prompts you for an initial set of parameters for the service.
ADD service
service
Specifies the name of the service to add to the configuration.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>ADD NNTP
[Adding new configuration entry for service "NNTP"]
Protocol: [TCP] TCP
TCP Port number: 119
Program to run: USER$DISK:[NNTP]NNTP_SERVER.EXE
[Added service NNTP to configuration]
[Selected service is now NNTP]
SERVER-CONFIG>
Detaches the terminal from the calling process and reattaches it to another process. Use the SPAWN SHOW PROCESS /SUBPROCESSES command to list the name of subprocesses. Use the DCL LOGOUT command to return to the original process. If the MULTINET_DISABLE_SPAWN logical is enabled, ATTACH does not work.
ATTACH process-name
process-name
Specifies the name of a process to which you want your terminal attached. (Not all subprocesses can be attached; some testing may be required.)
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SPAWN
$ MM
MM>SPAWN SHOW PROCESS /SUB
...
There are 3 processes in this job:
_TWA42:
PROC_1
PROC_2 (*)
MM>ATTACH _TWA42:
SERVER-CONFIG>ATTACH PROC_1
MM>QUIT
$ LOGOUT
SERVER-CONFIG>
This example shows the use and exit of attached subprocesses.
1. The first command uses SPAWN to create a subprocess. MM is invoked from the DCL command line. Next, the SPAWN SHOW PROCESS/SUB command is used to list all the subprocess names. The display shows that three subprocesses are active. (Process _TWA42: is SERVER-CONFIG, PROC_1 is MM, and PROC_2 is the SPAWN SHOW PROCESS/SUB command.)
2. In the next command, the MM ATTACH command returns control to the SERVER-CONFIG process. From this utility, ATTACH returns control to MM. To exit, QUIT is invoked from MM, and LOGOUT is entered at the original spawned DCL command line; finally control returns to SERVER-CONFIG. (If SPAWN SHOW PROCESS/SUB had been entered, only this command and the configuration processes would be active.)
Copies a given service entry. When a service is copied, the copy is disabled automatically. Enable the copy after changing any conflicting parameters, such as the port number.
COPY input-service output-service
input-service
Specifies the name of the service to duplicate.
output-service
Specifies the name of the service to create.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>COPY FINGER LOCALFINGER
[Adding service LOCALFINGER to configuration]
[Disabling service LOCALFINGER]
SERVER-CONFIG>
Deletes a given service from the current configuration. Once a service is deleted, all information about that service is removed. See the DISABLE command for disabling a service.
DELETE service
service
Specifies the name of the service to delete from the configuration.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>DELETE NNTP
SERVER-CONFIG>
Disables (removes) a given service from the current configuration. Unlike the DELETE command, all information about the service is retained and the service can be re-enabled at any time after a DISABLE.
DISABLE service
service
Specifies the name of the service to disable from the configuration.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>DISABLE NNTP
SERVER-CONFIG>
Enables a previously disabled service. (See DISABLE for information on disabling a service.)
ENABLE service
service
Specifies the name of the service to enable in the configuration.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>ENABLE NNTP
SERVER-CONFIG>
Saves the current configuration, if it has been modified, then quits.
EXIT
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>ENABLE NNTP
SERVER-CONFIG>EXIT
[Writing configuration to MULTINET_COMMON_ROOT:[MULTINET]
SERVICES.MASTER_SERVER]
$
Reads in a MultiNet server configuration file. After a GET, you can use the various configuration commands to modify this server configuration. (Functionally equivalent to USE.)
GET config_file
config_file
Specifies the name of the server configuration file to read in.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>GET ST_TMP:FOO.CONFIGURATION
[Reading in configuration from ST_ROO:[TMP]FOO.CONFIGURATION.1]
SERVER-CONFIG>
Invokes command help.
HELP [topics]
topics
Contains a space-delimited list of topics that begins with a topic followed by subtopics. The default topic is HELP.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>HELP ?
ADD ATTACH COPY DELETE DISABLE ENABLE
EXIT GET HELP NETCONTROL PUSH QUIT
RESTART SAVE SELECT SET SHOW SHUTDOWN
SPAWN STATUS USE VERSION WRITE
SERVER-CONFIG>
Transfers control to a configuration manager subsystem that contacts the NETCONTROL server at local or remote sites.
After invoking NETCONTROL, you can issue commands to the NETCONTROL server to affect MULTINET_SERVER operations at that site.
NETCONTROL [host]
The NETCONTROL server is usually protected from unauthorized access by a restriction list.
host
Specifies the name of the host to which to connect. If not specified, the default is the local host.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>NETCONTROL
Connected to NETCONROL server on "127.0.0.1"
<EXAMPLE.COM Network Control 5.6 (nnn) at Mon 15-Mar-2004 7:42am-EST
NETCONTROL>
Starts and attaches a DCL subprocess. If a parent process exists, attach to it. To return from DCL, use the ATTACH or the LOGOUT command. To switch back from a DCL subprocess, use the ATTACH command.
If the MULTINET_DISABLE_SPAWN logical is set, PUSH does not work.
PUSH
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>PUSH
$ LOGOUT
Process foobar_1 logged out at 16-Jun-2019 16:36:22.13
SERVER-CONFIG>
If the configuration file has been edited, QUIT prompts you to save the file before quitting.
QUIT
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>QUIT
$
Kills the old master server (MULTINET_SERVER) process and starts a new one. Any connections in progress are not interrupted. If the configuration has been modified since the last save, RESTART prompts you to save the configuration before restarting.
RESTART
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>RESTART
%RUN-S-PROC_ID, identification of created process is 2060005c
SERVER-CONFIG>
Writes the current MultiNet server configuration to a server configuration file. (Functionally equivalent to WRITE.)
SAVE config_file
config_file
Specifies the name of the file to which to write the current MultiNet server configuration (by default, the same file from which the configuration was read).
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SAVE
[Writing configuration to
MULTINET_COMMON_ROOT:[MULTINET]SERVICES.MASTER_SERVER.1103]
SERVER-CONFIG>
Selects which service will be modified by any subsequent SET commands.
SELECT service
service
Specifies the name of the service to select for modification.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT NNTP
[The Selected SERVER entry is not NNTP]
SERVER-CONFIG>
Specifies and maintains a list of hosts allowed access to the service. For IPv6 services IPv6 addresses and IPv4 addresses can be used. IPv4 addresses that are specified for an IPv6 service are treated as IPv4 mapped addresses.
SET ACCEPT-HOSTS
This example shows how to delete host 192.0.0.1 from the accept-hosts list, and add host 192.0.0.4.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET ACCEPT-HOSTS
Delete address "IP-192.0.0.1" ? [NO] Y
[Address "IP-192.0.0.1" deleted from TELNET]
Delete address "IP-192.0.0.2" ? [NO] RETURN
Delete address "IP-192.0.0.3" ? [NO] RETURN
You can now add new addresses for TELNET. An empty line terminates.
Add Address: 192.0.0.4
Add Address: RETURN
SERVER-CONFIG>
Invokes an interactive utility that prompts you for the addresses of networks that are allowed access to the selected service.
Specify each network as follows:
IP_address [subnetmask]
When done, press RETURN at the Add: prompt.
For more information about restricting access to services, see the MultiNet Installation and Administrator’s Guide.
SET ACCEPT-NETS
This example shows how to delete network address 192.0.0.0 from the accept-nets list, and add network address 128.1.0.0.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET ACCEPT-NETS
Delete address "IP-192.0.0.0" ? [NO] Y
[Address "IP-192.0.0.0" deleted from TELNET]
Delete address "IP-192.12.19.0" ? [NO] RETURN
You can now add new addresses for TELNET. An empty line terminates.
Add Address: 128.1.0.0
Add Address:
SERVER-CONFIG>
Specifies the number of server connections to queue up before refusing to accept additional connections when MAX-SERVERS is reached.
SET BACKLOG backlog
backlog
Specifies the number of connections to queue - but not process - while waiting for connections that are already running to exit.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET BACKLOG 5
[Backlog of TELNET set to 5]
SERVER-CONFIG>
Specifies the name of the internal MULTINET_SERVER routine to call when a connection request is received.
[none]
[tcp_connected]
[udp_chargen]
[udp_connected]
SET CONNECTED [udp_connected_single]
[udp_daytime]
[udp_discard]
[udp_echo]
[udp_time]
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET CONNECTED UDP_CONNECTED_SINGLE
[Connected action of TELNET set to UDP_Connected_Single]
SERVER-CONFIG>
Specifies and maintains a list of VMScluster nodes that cannot execute the service.
The master server (MULTINET_SERVER) can be tailored to enable or disable services on a per-node basis in a VMScluster. Use the SET ENABLED-NODES or SET DISABLED-NODES commands to specify a list of VMScluster nodes on which the service runs or does not run.
Note: The service must also be enabled via the ENABLE command.
|
Note: When entering the nodes to be disabled, use only the VMScluster node name or the DECnet node name; do not use the IP address.
|
SET DISABLED-NODES
This example shows how to delete the node FLEET from the disabled-nodes list, and add the node DRAGO.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET DISABLED-NODES
Delete VMScluster node "FLEET" ? [NO] Y
[Node "FLEET" deleted from TELNET]
Delete VMScluster node "NINET9" ? [NO] RETURN
You can now add new VMScluster nodes for TELNET. An empty line
terminates.
Add VMScluster node: DRAGO
Add Address: RETURN
SERVER-CONFIG>
Specifies and maintains a list of VMScluster nodes that can execute the service.
The master server (MULTINET_SERVER) can be tailored to enable or disable services on a per-node basis in a VMScluster. Use the SET ENABLED-NODES or SET DISABLED-NODES commands to specify a list of VMScluster nodes on which the service runs or does not run.
Note: The service must also be enabled via the ENABLE command.
Note: When entering the nodes to be enabled, use only the VMScluster node name or the DECnet node name; do not use the IP address.
Note: The service must also be enabled via the ENABLE command.
|
Note: When entering the nodes to be disabled, use only the VMScluster node name or the DECnet node name; do not use the IP address.
|
SET ENABLED-NODES
This example shows how to delete the node DRAGO from the enabled-nodes list, and add the node FLEET.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET ENABLED-NODES
Delete VMScluster node "DRAGO" ? [NO] Y
[Node "DRAGO" deleted from TELNET]
Delete VMScluster node "NINET9" ? [NO] RETURN
You can now add new VMScluster nodes for TELNET. An empty line
terminates.
Add VMScluster node: FLEET
Add Address: RETURN
SERVER-CONFIG>
Specifies a bit mask of flags that control the operation of the service. If you do not specify a flag for this command, all existing flags are cleared.
SET FLAGS [flag1 | flag2, ...]
EUNICE_SERVER
Indicates the connection is not closed until the server process exits, instead of when the server process closes the connection. This flag is required for servers compiled under EUNICE, as the EUNICE runtime opens and closes the channel to the connection many times.
EXOS_SERVER
Indicates that the MULTINET_SERVER process passes the connection to a new process using the EXOS conventions.
MANUAL
Indicates that the MULTINET_SERVER process does not accept a CHAOSnet connection; instead, the created process performs the accept in a nonstandard way.
NO_TELNET_NEGOTIATIONS
Indicates that TELNET option negotiations do not take place. This flag is used with services that use the Internal_Telnet INIT() routine.
SNMP_MONITORED
Tells the service handling routines to connect to SNMP Agent X and provide information about the state of the service. You need to define MULTINET_SNMP_AGENTX 1 and add AGENTX_PEER 127.0.0.1 in the SNMPD.CONF file. The values returned when SNMP_MONITORED flag is set are the Network Services Monitoring MIB (RFC2788). See the SNMP chapter in the MultiNet Installation and Administrator’s Guide for an example of the Network Services Monitoring MIB. The following values are displayed within enterprises.105.4.service_port:
1. Service name
2. Service port number
3. Maximum servers allowed
4. Number of active servers
5. Number of times the service processing code has been called
6. Last I/O status value for the service (generally 0 or 1)
START_AUX_SERVER
Causes the main master server to start the auxiliary master server process automatically.
UCX_SERVER
Configures services written for HP TCP/IP Services for OpenVMS to work with MultiNet.
This example sets the EUNICE_SERVER flag.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET FLAGS EUNICE_SERVER
[TELNET flags set to <EUNICE_SERVER>]
SERVER-CONFIG>
This example clears all flags that are set on a service.
SERVER-CONFIG>SET FLAGS
[TELNET flags set to <NONE>]
SERVER-CONFIG>
Specifies the name of the internal MULTINET_SERVER routine to call to initialize a service.
[cluster_alias_init]
[merge_image]
[netcontrol_init]
[none]
[rpc_init]
[rpc_portmap_init]
SET INIT [tcp_init]
[ucxqio_init]
[udp_init]
[viadecnet_init]
[viapsi_init]
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET INIT MERGE_IMAGE
[Init action of TELNET set to Merge_Image]
SERVER-CONFIG>
Sets keepalive timers for a service.
SET KEEPALIVE-TIMERS idle-time prove-interval probe-count
idle-time
Specifies the amount of time, in seconds, that a connection should be idle before the first keep alive probe is sent.
probe-interval
Specifies the number of seconds between keep alive probes.
probe-count
Specifies the number of probes that can be sent, with no reply from the other side of the connection, before the connection should be destroyed.
Keep alives are useful in situations when other systems that connect to services provided by your system are subject to frequent crashing, resets, or power-offs (as with personal computers).
TCP/IP connections must pass through a three-way handshake sequence to be closed and removed from the connection table. However, if a connection is open but idle, and the remote system is shut off, reset, or crashes, the connection cannot be closed down until an attempt to communicate with the remote system is made. If an application or service does not do this, a keep alive probe can be used to ensure that these dormant connections are cleaned up.
If you set the SO_KEEPALIVE socket option for a service, but you do not explicitly set the KEEPALIVE-TIMERS, the default values are:
· idle-time 2 hours
· probe-interval 75 seconds
· probe-count 8
If you do not set the SO_KEEPALIVE socket option for a service, no keep alive probes will be sent for connections to that service.
Specifies the name of the internal MULTINET_SERVER routine to call to listen for connections to the service.
[none]
SET LISTEN [tcp_listen]
[udp_listen]
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET LISTEN TCP_LISTEN
[Listen action of TELNET set to TCP_Listen]
SERVER-CONFIG>
Specifies the IP address that a service listens on. This parameter can be used to restrict a service to only accept incoming connections to a particular address configured on the system. Either an IPv4 or IPv6 address can be specified depending upon the socket-family that is set for the service.
SET LISTEN-ADDRESS 192.168.1.1
SET LISTEN-ADDRESS 2002:c0a8:101:1::1
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET LISTEN-ADDRESS 192.168.1.1
[Server will listen on 192.168.1.1]
SERVER-CONFIG>
Specifies whether to log successful connections to the service.
SET LOG-ACCEPTS mode
mode
If mode is TRUE, accepted connections are logged to OPCOM or to the log file; if it is FALSE, accepted connections are not logged.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET LOG-ACCEPTS TRUE
SERVER-CONFIG>
Specifies the destination of log messages: a VMS file name, or OPCOM to direct messages to the VMS OPCOM process.
SET LOG-FILE [opcom]
[file_spec]
file_spec
Specifies the file specification to which to write the audit records; specify OPCOM to write the audit records to OPCOM.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET LOG-FILE OPCOM
SERVER-CONFIG>
Specifies whether to log rejected connections to the service. A connection can be rejected because of the values of the REJECT-HOSTS, REJECT-NETS, and REJECT-BY-DEFAULT parameters.
SET LOG-REJECTS mode
mode
If mode is TRUE, rejected connections are logged to OPCOM or to the log file; if it is FALSE, rejected connections are not logged.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET LOG-REJECTS TRUE
SERVER-CONFIG>
Specifies the maximum number of service processes to allow at any one time. If this limit is reached, additional connections up to BACKLOG are accepted but are not processed until one of the previous connections completes.
SET MAX-SERVERS number
number
Specifies the maximum number of server processes to create for this service.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET MAX-SERVERS 4
[Max_Servers of TELNET set to 4]
SERVER-CONFIG>
Specifies service-dependent parameters. These parameters are passed to the initialization routine of built-in services. (This is normally not used for user-written services. The parameters and their arguments differ on a per-service basis.)
SET PARAMETERS
This example enables debugging for the Domain Name Service (DNS).
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT DOMAINNAME
SERVER-CONFIG>SET PARAMETERS
Delete parameter "bootfile
MULTINET:DOMAIN-NAME-SERVICE.CONFIGURATION"? [NO]
You can now add new parameters for DOMAINNAME. An empty line terminates.
Add Parameter: debug 3
Add Parameter:
[Service specific parameters for DOMAINNAME changed]
SERVER-CONFIG>
Specifies the VMS process priority to assign to created processes.
SET PRIORITY priority
priority
Specifies the VMS process priority to assign to created processes.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT SMTP
SERVER-CONFIG>SET PRIOITY 5
[Priority of SMTP set to 5]
SERVER-CONFIG>
Specifies that the service is to run in an auxiliary master server process rather than in the main master server process.
The SET PROCESS command should be used in conjunction with the SET FLAGS start_aux_server command, unless the administrator wants to start the auxiliary server manually.
SET PROCESS process_name
process_name
Specifies the name of the process to run in auxiliary master process mode.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET FLAG start_aux_server
SERVER-CONFIG>SET PROCESS MNSERVER_1
SERVER-CONFIG>SELECT RLOGIN
SERVER-CONFIG>SET FLAG start_aux_server
SERVER-CONFIG>SET PROCESS MNSERVER_1
SERVER-CONFIG>SELECT RSHELL
SERVER-CONFIG>SET FLAG start_aux_server
SERVER-CONFIG>SET PROCESS MNSERVER_1
SERVER-CONFIG>
Specifies the VMS file name of the image to run or merge.
SET PROGRAM file_spec
file_spec
Specifies the name of the file containing the server image.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT SMTP
SERVER-CONFIG>SET PROGRAM
MULTINET:SMTP_SERVER.EXE
[Program to run for SMTP set to MULTINET:SMTP_SERVER.EXE]
SERVER-CONFIG>
Specifies whether to reject a connection from a host that does not match any of the ACCEPT-HOSTS, ACCEPT-NETS, REJECT-HOSTS, and REJECT-NETS lists.
SET REJECT-BY-DEFAULT mode
mode
If mode is TRUE, the default is to reject connections; if it is FALSE, the default is to accept them.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT SMTP
SERVER-CONFIG>SET REJECT-BY-DEFAULT TRUE
SERVER-CONFIG>
Specifies the size of the receive socket buffers.
SET RECEIVE-BUFFER-SPACE size
size
Specifies the size of the receive socket buffers for the selected service.
Specifies and maintains a list of hosts that are not allowed to access the service. For IPv6 services IPv6 addresses and IPv4 addresses can be used. IPv4 addresses that are specified for an IPv6 service are treated as IPv4 mapped addresses.
SET REJECT-HOSTS
This example shows how to delete host 192.0.0.1 from the reject-hosts list, and add host 192.0.0.4.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET REJECT-HOSTS
Delete address "IP-192.0.0.1" ? [NO] Y
[Address "IP-192.0.0.1" deleted from TELNET]
Delete address "IP-192.0.0.2" ? [NO] RETURN
Delete address "IP-192.0.0.3" ? [NO] RETURN
You can now add new addresses for TELNET. An empty line terminates.
Add Address: 192.0.0.4
Add Address:
SERVER-CONFIG>
Specifies a text string to send down the network connection when a service is rejected.
SET REJECT-MESSAGE string
string
This parameter is written down the network connection before closing the connection when a request is rejected.
This parameter is ignored on UDP services.
This example sets the rejection message to "Service refused."
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET REJECT-MESSAGE Service refused
SERVER-CONFIG>
Specifies and maintains a list of networks or subnetworks that are not allowed to access the service.
SET REJECT-NETS
SET REJECT-NETS invokes an interactive utility that prompts you for the addresses of networks that are not allowed to access the selected service.
Specify each network as follows:
IP_address [subnetmask]
When done, press RETURN at the Add: prompt.
For more information about restricting access to services, see the MultiNet Installation and Administrator’s Guide.
This example deletes network address 192.0.0.0 from the reject-nets list, and adds network address 128.1.0.0.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET REJECT-NETS
Delete address "IP-192.0.0.0" ? [NO] Y
[Address "IP-192.0.0.0" deleted from TELNET]
Delete address "IP-192.12.19.0" ? [NO] RETURN
You can now add new addresses for TELNET. An empty line terminates.
Add Address: 128.1.0.0
Add Address:
SERVER-CONFIG>
Specifies the size of the send socket buffers.
SET RECEIVE-BUFFER-SPACE size
size
Specifies the size of the send socket buffers for the selected service.
Specifies the name of the internal MULTINET_SERVER routine to call to perform the service.
[internal_ftp]
[internal_pop2]
[internal_pop3]
[internal_telnet]
SET SERVICE [no_service]
[none]
[run_program]
[tcp_daytime]
[tcp_time]
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET SERVICE INTERNAL_TELNET
[Service action of TELNET set to Internal_Telnet]
SERVER-CONFIG>
Changes the name of the service.
SET SERVICE-NAME name
name
Specifies the new service name.
This example shows how to rename a service to "FOO."
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET SERVICE-NAME FOO
[Name of selected service changed to FOO]
SERVER-CONFIG>
For SPX- or IPX-based servers, sets the service type advertised for the service. This setting is generally not changed by users.
SET SERVICE-TYPE service-type
service-type
Specifies the service type for SAP advertisements. This value is a decimal number in the range of 1 through 6535.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT servicename
SERVER-CONFIG>SET SERVICE-TYPE n
[servicename service type is n]
SERVER-CONFIG>
Specifies the address family of the service.
SET SOCKET-FAMILY family
family
Specifies the new protocol family for this service.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET SOCKET-FAMILY AF_INET
[TELNET socket family is AF_INET]
SERVER-CONFIG>
Specifies socket options to be set via setsockopt(). See the MultiNet Programmer’s Reference for more information on socket options.
SET SOCKET-OPTIONS options
options
Specifies a list of socket options separated by a vertical bar (|).
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET SOCKET-OPTIONS SO_DEBUG |
SO_KEEPALIVE
[TELNET socket options set to <SO_DEBUG | SO_KEEPALIVE]
SERVER-CONFIG>
Specifies the port number on which to listen for connections.
SET SOCKET-PORT port
port
Specifies the name or number of the port on which to listen.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TELNET
SERVER-CONFIG>SET PORT 10
[TELNET socket port is now 10]
SERVER-CONFIG>
Specifies the type of socket; for example, SOCK_STREAM (TCP) or SOCK_DGRAM (UDP).
SET SOCKET-TYPE type
type
Specifies the socket type to listen on, usually SOCK_ DGRAM (UDP) or SOCK_STREAM (TCP).
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT TFTP
SERVER-CONFIG>SET SOCKET-TYPE SOCK_DGRAM
[Socket type of TFFTP set to SOCK_DGRAM]
SERVER-CONFIG>
Specifies the user name under which the selected service is started.
SET USERNAME username
username
Specifies the name of the user under which the selected service is started.
Specifies how much memory the process will be allowed to use if there are free pages available.
SET WORKING-SET-EXTENT
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT FTP
SERVER-CONFIG>SET WORKING-SET 2000
[Working_Set of FTP set to 2000]
SERVER-CONFIG>
$ MULTINET CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6(nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT FTP
[The Selected SERVER entry is now FTP]
SERVER-CONFIG>SET WORKING-SET-QUOTA 4096
[Working Set Quota of FTP set to 4096]
SERVER-CONFIG>SET WORKING-SET-EXTENT 8192
[Working Set Extent of FTP set to 8192]
Specifies the maximum amount of memory the process can lock into its working set.
SET WORKING-SET-QUOTA
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT FTP
SERVER-CONFIG>SET WORKING-SET 2000
[Working_Set of FTP set to 2000]
SERVER-CONFIG>
$ MULTINET CONFIGURE /SERVERS
MultiNet Server Configuration Utility
5.6(nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SELECT FTP
[The Selected SERVER entry is now FTP]
SERVER-CONFIG>SET WORKING-SET-QUOTA 4096
[Working Set Quota of FTP set to 4096]
SERVER-CONFIG>SET WORKING-SET-EXTENT 8192
[Working Set Extent of FTP set to 8192]
Shows the current server configuration.
SHOW
/FULL
Provides a more detailed listing.
This example displays detailed information about SMTP.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SHOW/FULL SMTP
Service "SMTP"
TCP socket (AF_INET,SOCK_STREAM), Port 25
Socket Options = SO_KEEPALIVE
INIT() = TCP_Init
LISTEN() = TCP_Listen
CONNECTED() = TCP_Connected
SERVICE() = Run_Program
Program = "MULTINET:SERVER_SMTP.EXE"
SERVER-CONFIG>
Stops the master server (MULTINET_SERVER) process. After a SHUTDOWN, any subsequent network service requests are rejected by MultiNet until the RESTART command is executed.
SHUTDOWN
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SHUTDOWN
SERVER-CONFIG>
Executes a single DCL command, or if entered without options, starts a subprocess with the same effect as PUSH. To return from DCL, use the LOGOUT command. If the MULTINET_DISABLE_SPAWN logical is set, SPAWN does not work.
SPAWN [command]
command
Specifies a command to execute. If you omit command, a DCL command line subprocess is created.
/INPUT=file-spec
Specifies an input file to the command you enter with SPAWN.
/LOGICAL_NAMES
/NOLOGICAL_NAMES
Specifies that logical names and logical name tables are not copied to the subprocess.
/SYMBOLS
/NOSYMBOLS
Specifies that global and local names are not passed to the subprocess.
/WAIT
/NOWAIT
Returns control without waiting for the command to complete. Do not use this qualifier with commands that have prompts or screen displays.
/OUTPUT=file-spec
Specifies a file that retains the output of the command invoked with SPAWN. This qualifier only works when a single command is entered without creating a DCL subprocess. In addition, this qualifier is positional; you must enter it immediately after SPAWN or other qualifiers.
This example displays terminal information, captures the output in a file, then displays the information with the TYPE command.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SPAWN/OUTPUT=FOO. SHOW TERM
SERVER-CONFIG>SPAWN TYPE FOO.
...
This example invokes a command procedure.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SPAWN @COMPROC
...
This example displays help information about the SERVER-CONFIG utility. Use the LOGOUT command to return control to SERVER-CONFIG.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>SPAWN
$ HELP MULTINET CONFIGURE /SERVER
...
$ LOGOUT
SERVER-CONFIG>
Shows the status of the MultiNet server configuration program.
STATUS
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6(nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>STATUS
This is the MultiNet server configuration program Version 5.5(nnn)
There are 65/8192 entries in the current server configuration.
There is NO selected SERVER entry.
The configuration MULTINET:SERVICES.MASTER_SERVER is not modified.
SERVER-CONFIG>
Reads in a MultiNet server configuration file. After a USE, you can use the various configuration commands to modify the server configuration. (Functionally equivalent to GET.)
USE config-file
config-file
Specifies the name of the server configuration file to read in.
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>USE ST_TMP:FOO.CONFIGURATION
[Reading in configuration from ST_ROOT:[TMP]FOO.CONFIGURATION.1]
SERVER-CONFIG>
Displays the MultiNet server configuration program version and release information.
VERSION
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>VERSION
This is the MultiNet Server configuration program Version 5.6 (nnn)
SERVER-CONFIG>
Writes the current server configuration file. (Functionally equivalent to SAVE.)
WRITE config-file
config-file
Specifies the name of the file to which to write the current MultiNet server configuration (by default, the same file from which the configuration was read).
$ MULTINET
CONFIGURE /SERVERS
MultiNet Server Configuration Utility 5.6 (nnn)
[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]
SERVER-CONFIG>WRITE
[Writing configuration to MULTINET_COMMON_ROOT:[MULTINET]SERVICES.MASTER_SERVER.1103]
SERVER-CONFIG>