5.4
Table Of Contents
- Avid iNEWS Setup & Config Guide
- Contents
- Using This Guide
- Introduction
- The iNEWS Console
- Getting Started
- Users
- The Database: Directories, Queues, and Stories
- Overview of the iNEWS Database
- Restrictions to Directory or Queue Creation
- Creating a New Directory
- Creating a New Queue
- Creating a New Story
- Using Script Templates
- Renaming a Directory or Queue
- Deleting a Directory or Queue
- Recovering a Killed Story
- Viewing Database Traits
- Changing Database Traits
- Database Purge Intervals and Limits
- Identifying Locked Queues and Stories
- Removing Locks from a Workstation
- Unbusy Stories and Queues
- MOS Integration
- Groups
- Overview of Groups
- Viewing Group Information from the Console
- Viewing Group Information from a Workstation
- Creating a New Group
- Group Checker
- Renaming a Group
- Deleting a Group
- Creating or Modifying Multiple Groups
- Adding Users as Members of a Group
- Adding Groups as Members of Other Groups
- Adding Workstations as Members of a Group
- Combined Permissions and Timeouts
- Group Access and Usage Restrictions
- Group Traits for the Database
- Creating a Mail Alias
- Keyboards and Macros
- Forms
- Character Generator Title Entry
- System Configuration
- Printers
- Wires
- Servers
- iNEWS Community
- MOS Redirection
- Web Publishing
- iNEWS Projects
- Media | Index
- Command References
- Programs Invoked by iNEWS
- Commands Used by Avid Personnel Only
- Linux Commands Used in iNEWS
- Console Server Commands
- broadcast
- configure
- connect
- ctraits
- dbclean
- dbclose
- dbdev and dbsize
- dbdump
- dbfree
- dblines
- dboriginal
- dbpurge (Superuser conditional)
- dbrestore
- dbserver
- dbsort
- dbtraits
- dbvisit
- dictionary
- diskclear (Superuser only)
- diskcopy
- doc
- ed
- enter
- force (Superuser only)
- grpcheck
- gtraits (Superuser only)
- help
- hogs
- idiff
- list
- list B
- list C
- list c
- list d
- list g
- list p
- list q
- list s
- list sq
- list u
- logout
- makemontab
- makeshift (Super user only)
- maketab (Superuser only)
- mapcheck
- msgclean
- offline
- online
- otod
- reconnect
- remove
- rename (Superuser only)
- reorder
- restart
- searchtape
- send
- sendlong
- shutdown
- sitedump (Superuser only)
- siterestore (Superuser only)
- startup
- status
- stop
- su
- unbusy
- utraits (Super user only)
- version
- wholockedit
- Job List Commands
- Dialog Commands
- System Files
- Standard Dictionaries
- Using Dictionaries to Define Messages and Commands
- Customizing Dictionaries
- Utility Messages Dictionary (/site/dict/messages)
- DBServer Program Messages
- Disconnect Program Messages
- Category and Keyword Check Program Messages
- Keyboard Check Program Messages
- Keyboard Check Program Messages for Macros
- Grpcheck Messages
- Wire Program Messages
- Mail Server Messages
- Map Check Program Messages
- Validation (Action) Server
- Seek Server Messages
- Last Login Messages
- Print Server Messages
- dbtraits Messages
- Save Error (Workstation) Messages
- Queues Dictionary (/site/dict/queues)
- Words Dictionary (/site/dict/words)
- Keyboard Macros Dictionary (/site/dict/keymacros)
- Case-shifting Dictionary (/site/dict/shift)
- MCS Dictionary (/site/dict/mcs)
- Job List Command Dictionary (/site/dict/joblist)
- D Messages Dictionary (/site/dict/dmessages)
- S Messages Dictionary (/site/dict/smessages)
- Environment Variables
- Managing Traits at the Console
- The Line Editor, ed
- Index
Adding a Server Program to the System
316
Adding a Server Program to the System
The overall process of creating a server is the same for all server utility programs.
To add a server to iNEWS:
1. Check the configuration file (/site/config) and choose an available device number for the
server. Device numbers can range from 1 to 5000. Take note of existing device ranges in
your /site/config file. There might already be servers of the type you are adding. If possible,
add your new server to the end of the number range the existing servers use. When setting
number ranges, be sure to allow for expansion.
2. Add the server program to the configuration file on each iNEWS Server—such as server A
and server B—in your system.
c
Always back up the /site/config file before making any changes. See “Editing the
Configuration File” on page 253 for more information.
a. Select all iNEWS Servers.
b
. Open and edit the configuration file, by typing (what appears in bold):
NRCS-A$ ed /site/config
1259
After you press Enter, the editor responds by displaying a numerical value indicating the
file size expressed as the number of characters, including spaces and returns.
n
This procedure, which modifies the /site/config file uses ed, the line editor. If you do not know
how to use ed to modify lines in the file, please see “The Line Editor, ed” on page 647.
c. Add the server program’s device number to the serv
ers line in the host section(s) of the
configuration file for the iNEWS Server on which the server program will run. For
instance:
servers 257 258 259
260
The device number 260 is added to the servers line in this example.
d. Add a configuration line for the server program. This line should contain the mailbox
number assigned to the server program, when necessary.
n
Divide your server programs evenly among your iNEWS Servers to distribute the load they put
on your system. Additionally, ensure that you modify the servers line for alternate host
definitions for your iNEWS Servers to include the server program’s device number. This ensures
the server program can run on the surviving computer should one of your iNEWS Servers stop
functioning. See “Configuration File” on page 250 for more information.
The format for server programs’ configuration lines are:
server <device #> <type> <mailbox> <device name>