HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

281

282

283

284

285

286

287

288

289

290

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man4/!!!intro.4

________________________________________________________________

___ ___

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

NAME

services.window - ﬁle containing applicationsand their associated memory window id

DESCRIPTION

The ﬁles /etc/services.window is used by applications using memory windows.

Each line in the /etc/services.window ﬁle associates an application with a memory window id. A

line in the /etc/services.window ﬁle cannot start with a space or tab. The format is a unique

name, deﬁning the application, followed by a space/tab, followed by a unique window_id. See the sample

ﬁle 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 applicationsin 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 win-

dow allows for the deﬁnition of a unique 1 gigabyte quadrant and since multiple memory windows can be

deﬁned in a system, the system total for shared resources can exceed the 1.75 gigabyte limitation for 32 bit

processes.

The deﬁnition of a memory window is only available for 32-bit processes.

The /etc/services.window

ﬁle 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 ﬁxed.

A memory window application uses the command getmemwindow(1M) to extract the application’s

window_id from the

/etc/services.window

ﬁle, and then passes that id to the setmemwindow(1M).

Using the same window id places applications in the same memory window.

EXAMPLE

Below is a example

/etc/services.window

ﬁle.

# /etc/services.window

application1 20

application2 30

application3 40

AUTHOR

services.window was developed by HP.

FILES

/etc/services.window File containing applications’ associated window id.