*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->HP-UX 11i man pages -> services.window (4)              


 services.window(4)                                       services.window(4)

 NAME    [Toc]    [Back]
      services.window - file containing applications and their associated
      memory window id

 DESCRIPTION    [Toc]    [Back]
      The files /etc/services.window is used by applications using memory

      Each line in the /etc/services.window file associates an application
      with a memory window id.  A line in the /etc/services.window file
      cannot start with a space or tab.  The format is a unique name,
      defining the application, followed by a space/tab, followed by a
      unique window_id.  See the sample file in EXAMPLES.

      Memory windows allows for the starting of a process in a unique or
      existing memory window where it can create and share objects with
      other applications in the same memory window.

      The creation of memory windows removes the system wide restriction on
      shared resources.  Without memory windows, 32-bit processes were
      limited to 1.75 gigabytes of shared resources.  Each memory window
      allows for the definition of a unique 1 gigabyte quadrant and since
      multiple memory windows can be defined in a system, the system total
      for shared resources can exceed the 1.75 gigabyte limitation for 32
      bit processes.

      The definition of a memory window is only available for 32-bit

      The /etc/services.window file provides a central place for memory
      window applications to associate their memory window ids.  In the
      event there are any collisions, only a change in /etc/services.window
      is necessary to select another memory window for the entire
      application.  If /etc/services.window is not used, and user
      applications hard code window id's in their startup scripts,
      collisions are not easily detected or easily fixed.

      A memory window application uses the command getmemwindow(1M) to
      extract the application's window_id from the /etc/services.window
      file, and then passes that id to the setmemwindow(1M).

      Using the same window id places applications in the same memory

 EXAMPLE    [Toc]    [Back]
      Below is a example /etc/services.window file.

      # /etc/services.window
      application1  20
      application2  30

 Hewlett-Packard Company            - 1 -   HP-UX 11i Version 2: August 2003

 services.window(4)                                       services.window(4)

      application3  40

 AUTHOR    [Toc]    [Back]
      services.window was developed by HP.

 FILES    [Toc]    [Back]
      /etc/services.window          File containing applications' associated
                                    window id.

 SEE ALSO    [Toc]    [Back]
      setmemwindow(1M), getmemwindow(1M), 11.0 Memory Window White Paper.

 Hewlett-Packard Company            - 2 -   HP-UX 11i Version 2: August 2003
[ Back ]
 Similar pages
Name OS Title
portal HP-UX a "window to the future" for applications
winterm IRIX provides a uniform interface for launching applications which need a window shell (terminal emulator)
license.dat IRIX license configuration file for FLEXlm licensed applications
license.options IRIX site administrator options file for FLEXlm licensed applications
setmemwindow HP-UX changes the window id of a running program or starts a program in a particular memory window
copylist IRIX copy a file into memory
msync Linux synchronize a file with a memory map
core OpenBSD memory image file format
core Tru64 Format of memory image file
core FreeBSD memory image file format
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service