Avaya Media Processing Server Series System (Software Release 2.1) Manual do Utilizador Página 129

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 306
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 128
Base System Configuration
# P0602477 Ver: 3.1.11 Page 129
File Based Shared Memory (FBSM) is not transient by default (as Solaris shared
memory is) and is not removed or cleared when all applications exit or when the
machine reboots (unless the FBSM is located in /tmp on Solaris). VENGINE's
command line option -K is ignored for FBSM.
Use the following vassm utility option to remove a specified shared memory item:
vassm -c -i <itemname>
Normally, all Constant Shared Memory (CoSM) items reside in the directory specified
by the SharedMemory entry in this file. However, they can be placed into a separate
directory if the ase.conf file has the second entry ConstSharedMemory:
constdir, where constdir represents this separate directory.
While the SharedMemory dirname entry must always reside on a local partition
and have read/write permissions, the constdir directory may be located on a
mounted read-only file system. This allows CoSM items to be shared over a
distributed environment. Note that all CoSM initialization must be performed on the
machine where the files are physically located.
Both the dirname and contsdir directories can reside on a shared file system.
ASE relies on certain keywords defined in this file. However, a developer can add any
arbitrary name:value pair to the file and extract it in an application by using the
get-configuration CALL function. For more information on using CALL
functions, and for information on vexlinking, see the PeriProducer User’s Guide. To
find out more about Shared Memory, see the PeriView Reference Manual.
The /etc/services File
The services file contains a list of processes (i.e., the services), some of which
may be accessed by call processing or administrative applications. The file defines
the port and protocol associated with each service and is used by the ASE
(Application Services Environment) software process group.
VMST is aliased as vms in this file, but should not be confused with previous (“non-
extended”) versions of VMS.
The following are sample excerpts of this file, followed by an explanatory table:
Vista de página 128
1 2 ... 124 125 126 127 128 129 130 131 132 133 134 ... 305 306

Comentários a estes Manuais

Sem comentários