Broadcast Tools SS 4.1 III Bedienungsanleitung Seite 16

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 140
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 15
The operation of each of these modules is explained in detail in the chapters that follow.
However, we first need to cover some basic concepts common to all Rivendell modules.
Section 1.1 The Rivendell Security Paradigm
All Rivendell modules make use of the following four classes of system resources:
Hosts
Users
Groups
Services
We'll cover each of these concepts in turn.
1.1.0 Hosts
Every physical computer within a given network that is running Rivendell software is
referred to as a host. Any host in a Rivendell network can be individually configured and
controlled from any other host (provided the system administrator has enabled this
capability). Hosts can be used for a wide variety of applications, including content
ingestion and management, automatic recording (sometimes referred to as netcatching),
on-air play out or log (sometimes also referred to as playlist) generation. It is also
possible for a single host to perform all of these functions.
1.1.1 Users
Every host on a Rivendell network has one or more users available to it. In this context,
a 'user' is merely a set of access policies established by the system administrator that
defines what tasks a given host is or is not allowed to perform. Every host has at least
one user, called the default user. As the name suggests, this is the set of user policies
that are loaded by default when the system starts up. It is also possible to change the user
currently in use on a given host by running the RDLogin module.
1.1.2 Groups
A Rivendell group is a system of categories that is used by the audio library to classify
and organize the audio within the library. Groups are a very powerful capability, and
many operations within Rivendell can be specified on the basis of group membership.
The actual classification scheme, including the number of available groups and their
names, is completely arbitrary so as to allow each facility to tailor a schema that best fits
its own operational requirements. Designing and implementing the group schema is one
of the most important tasks facing the Rivendell system administrator, as a well-designed
schema can make long-term maintenance and management of the system substantially
easier vis-a-vis a poorly thought out one. We will cover groups in detail in the chapters
devoted to the RDLibrary and RDAdmin modules.
Seitenansicht 15
1 2 ... 11 12 13 14 15 16 17 18 19 20 21 ... 139 140

Kommentare zu diesen Handbüchern

Keine Kommentare