Kbase 12289: Why Does PROGRESS VAX/VMS need those PRIVILEGES?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Why Does PROGRESS VAX/VMS need those PRIVILEGES?
This notebook entry describes why PROGRESS needs privileges to operate
efficiently on VAX/VMS.
Images should be granted to executables installed in Shared Memory.
PRIVILEGES WHY PROGRESS NEEDS THEM
---------- ----------------------------------------------------
GROUP To wake up processes in the same groups that are in
a hibernation state with the VAX/VMS System Service
Call SYS$WAKE.
WORLD To wake up processes that are outside the server's
group with the VAX/VMS System Service Call SYS$WAKE.
SYSLCK To obtain a VMS System Lock in the user control
table when a login is initiated. It takes out a
VMS SYSTEM LOCK on shared memory during the user
login.
SYSGBL So that PROGRESS processes (in particular server
processes that are spawned in a client/server
environment) can allocate global pages of memory.
SYSNAM To manipulate and create logical table information.
The Server needs this privilege to work with logical
assignment during the creation of mailbox channels.
DETACH To spawn a process that has a different User
Identification Code (UIC) than the user who started
the broker/servers.
SYSPRV To create mailboxes with different UICs and GROUPS
than the server process.
NOTE: This privilege is only needed for the broker
executable. It is not needed for the client. If
used, this can create a security issue if users get
access to the Progress editor.
SETPRV So that gateway servers can save/alter/restore
process UICs. This privilege is only necessary for
GATEWAY images.
Progress Software Technical Support Note # 12289