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
Overview
246
n
The Linux graphical X-window login offers additional Linux GUI tools for system management.
Tasks such as changing IP addresses and checking hardware are much easier within the
X-window GUI. However, if all iNEWS Servers have the GUI installed as part of the Linux
installation, it does take additional resources to run and requires additional hardware, such as
monitor, keyboard, and mouse. Some system managers might not want to run the GUI full-time so
as to reserve memory and other resources for the iNEWS Server processes.
While the impact of running the GUI is probably not terribly significant on modern hardware
with speedy processors and plenty of RAM, Avid does not test the software or system
performance with the GUI running. This editing alternative is not required or supported by Avid.
Before editing any system file, Avid recommen
ds you make a backup copy of the file.
Making a Backup File
When you want to make changes to a system file, begin by making a backup copy of the file, and
then edit the backup file. That way, if you make a mistake during the editing process, your
original file version is preserved.
To make a backup copy of a file:
t Use the copy command at the console in the following format:
cp <file pathname> <new pathname>
For instance, to copy the configuration file in the Site directory, type:
NRCS-A$ cp /site/config /site/config.backup
Viewing System Files
When viewing a system file, use the more command at the console.
The format is:
more <file pathname>
The more command allows you to view one page at a time, which is especially useful for really
long files. The cat command may also be used, particularly for smaller files.
To use the more command to view your copy of the configuration file:
t Type:
NRCS-A$
more /site/config.test
Information similar to the following example appears: