# Configuration file for the iservd process # # $RCSfile: iservd.conf.sample,v $ # $Revision: 1.1 $ # $Date: 1998/08/03 16:54:26 $ # # $Header: //Iservd/iservd.conf.sample#1 $ # #syntax: # iservd [config file] # # default config file is /etc/iservd.conf # # Format is : # device_name server_host port options # # Note: An argument and its parameter need to be separated by a space or tab. # For example, "-d 20" is valid. The command "-d20" would be flagged # as a syntax error. You may also type iservd -help. # # Comment lines must have a '#' in the first column # # where options are: # # -d #secs - seconds delay between retries < default 5,min 1, no max> # if a read/write/connect call fails. # # -l file_name - output file path and name. Process # transitions will be written to file_name. # # -m - Turn OFF binary mode. Normally the iservd process will be in # binary mode and will send the IntelliServer a message saying # so. Turning OFF binary mode will have the iservd process add # NULL '\0' after \r except if sequence of \r\n. # Received packets will parse newlines and NULLs after # carriage returns. Use -b option if the user wants telnet # message processing. # # -o - Old version of IntelliServer. Doesn't do telnet negotiation. # This is for backwards compatibility only. # # -p - Initiate a permanent connection. # Ideally for modems and getty connections. Connections are # temporary by default. More comments on permanent connections # appear below. # # -r num - number of retries before quitting to connect to server. # < default 128,no max, neg value means try forever > # # -t #secs - number of seconds to timeout connection to server # due to no traffic. For temporary connections. # # # -v [a|h|d| - View data sent from host to the IntelliServer. This # flag must be used with the debug option (below) or else # the flag is ignored. # Use 'a' to denote ASCII dump, 'h' for hexadecimal dump, # or 'd' for decimal dump. # # -w #secs - Number of seconds to wait before closing the socket. # Only meaningful for temporary connections AND the old # version flag (-o) is used. It doesn't have an affect on # permanent connections. # # On some systems the socket will close before a process # can send any unsent data. If you notice that some of # your print jobs are truncated it may be due to a premature # close so you would want to use this option. # # The value used must be non-negative and should not need to be # greater than five. Two seconds is recommended. The # actual value should be tuned for your system. A value of zero # (the default) means the system will use the socket linger # option only. # # If the linger call works on your system then you will # never need to use this option. # # -x - Turn on debug mode. A file "device_name".debug will be created # by if the -l option isn't used. Otherwise the log file will # be used. Created in /tmp. # -I - Turn on the remote shell option. Whenever there is a connection # refused from Intelli-server, this option is used to do a remote # kill port. # # Permanent connections are usually used for cluster (getty) # connections and for modem connections. Non permanent are # typically used for printer jobs. # # To set up a permanent pool of modems. The device names # will be different but the host and port numbers will # be the same. # # iservd will not check for unique device names. # It is up to the user to make sure the device name is unique. # # Typically you want to start the iservd during system startup by # adding a file to your /etc/rcX.d directory. Where X is the run level # which starts up tcp/ip daemons. The iservd must start AFTER tcp has # started. # # If restarting by hand. # - kill all iservd processes # - remove the device name from /dev directory # (Especially if it has a getty running on it) # - kill any gettys associated with permanent connections. # - send kill -1 signal to init if changes were made to the # ttytab/inittab files which affect device_names in this file. # - restart iservd # # Note - Iservd will fork off a process to handle each device. # If the connection is TEMPORARY, the iservd child is forked when i/o # is passed to the device. This child will pass the data to the # IntelliServer # # If the connection is PERMANENT, the iservd child is forked as soon as # a connection is established to the IntelliServer. # # # Sample entries # # Use /dev/laser to access port 0 on server mustang. # #laser: mustang 9000 -p # # Retry 20 times if failure. # #cobra11: cobra 9011 -r 20 # # Retry 40 times with delay of 3 seconds between each failure. # #cobrap: cobra 9010 -r 40 -d 3 # # Permanent connection ,log entries to file cobra12 , turn on debugging. # #cobra12: cobra 9012 -p -l cobra12 -x # # Log entries to file cobra13 with debug on also dump traffic to # the server to the file for viewing as alphanumeric characters. # #cobra13: cobra 9013 -l cobra13 -x -v a # # Wait 3 seconds before closing the socket. (Use if OS doesn't support linger). # #laser2: mustang 9001 -w 3 # # Create group of 2 devices as Group 1 on cobra. # #cobra1: cobra 10001 #cobra2: cobra 10001 # # you may also create tty devs and run gettys on them! # make sure these devs do not already exist as they will be replaced #ttyI00: iserver 9000 -p -x #ttyI01: iserver 9001 -p -x #ttyI02: iserver 9002 -p -x #ttyI03: iserver 9003 -p -x #ttyI04: apache 9004 -p -x -l apache4 -R #ttyI05: apache 9005 -p -x -l apache5 -R #ttyI06: iserver 9006 -p -x #ttyI07: iserver 9007 -p -x #ttyI00: apache 9000 -p -x -vh -l apache0 -R -M 5 -h #ttyI00: apache 9000 -p -x -l apache0 -R -I -M 5 -h -D #ttyI09: apache 9009 -p -x -vh -l apache9 -R 4050 ras2000 9003 -p hap ras2000 9000 -p hpland ras2000 9005 -p 3870 ras2000 9004 -p