System User and Group Management in OES 2 SP3
281
I.8 System Groups
These are groups in the local Linux system that provide a group ID (gid) to an OES process.
When NSS is installed, some of these groups are moved to eDirectory and LUM enabled. This is
done to provide access to NSS data and to keep group IDs the same across multiple servers.
Table I-2
lists the system groups that are used by OES services.
dhcpd
DHCP
DHCP accesses local resources through this or an alternatively
specified user.
If the DHCP lease and configuration files are stored on NSS, the
user must be moved to eDirectory and LUM enabled.
dhcpd
is used by default, but any local user can be used.
hacluster
Heartbeat
This user is created by Heartbeat, but it not used by Heartbeat nor
by Novell Cluster Services.
iprint
iPrint
The iPrint daemons run as this user.
If iPrint is moved to NSS, this user is created in eDirectory and the
local user is removed.
named
DNS
This system user lets DNS access local resources.
In case of clusters, DNS data is on NSS volume, and so the user
has to be created in eDirectory as well.
named
is used by default, but any local user can be used.
ncsclient
NCS
Used by NCS to access the adminfs file system.
novell_nobody CIMOM
This user is created by CIMOM but is not currently used.
novlxregd
XTier
The XTier Registry Daemon (novell-xregd) runs as this user.
When NSS is installed on the Linux server, this user is removed
from the local system and created as LUM-enabled user in
eDirectory. This is required because it must have access to NSS
data, and all NSS access is controlled through eDirectory.
novlxsrvd
XTier
The XTier Server Daemon (novell-xsrvd) runs as this user.
When NSS is installed on the Linux server, this user is removed
from the local system and created as LUM-enabled user in
eDirectory. This is required because it must have access to NSS
data, and all NSS access is controlled through eDirectory.
wwwrun
Apache
The Apache daemon runs as this user.
When NSS is installed on the Linux server, this user is removed
from the local system and created as LUM-enabled user in
eDirectory. This is required because it must have access to NSS
data, and all NSS access is controlled through eDirectory.
System User or
Group Name
Associated Service
Purpose
Summary of Contents for OPEN ENTERPRISE SERVER - CONVERSION GUIDE 12-2010
Page 12: ...12 OES 2 SP3 Planning and Implementation Guide...
Page 24: ...24 OES 2 SP3 Planning and Implementation Guide...
Page 50: ...50 OES 2 SP3 Planning and Implementation Guide...
Page 74: ...74 OES 2 SP3 Planning and Implementation Guide...
Page 78: ...78 OES 2 SP3 Planning and Implementation Guide...
Page 80: ...80 OES 2 SP3 Planning and Implementation Guide...
Page 96: ...96 OES 2 SP3 Planning and Implementation Guide...
Page 146: ...146 OES 2 SP3 Planning and Implementation Guide...
Page 176: ...176 OES 2 SP3 Planning and Implementation Guide...
Page 210: ...210 OES 2 SP3 Planning and Implementation Guide...
Page 218: ...218 OES 2 SP3 Planning and Implementation Guide...
Page 226: ...226 OES 2 SP3 Planning and Implementation Guide...
Page 234: ...234 OES 2 SP3 Planning and Implementation Guide...
Page 236: ...236 OES 2 SP3 Planning and Implementation Guide...
Page 244: ...244 OES 2 SP3 Planning and Implementation Guide...
Page 246: ...246 OES 2 SP3 Planning and Implementation Guide...
Page 250: ...250 OES 2 SP3 Planning and Implementation Guide...
Page 254: ...254 OES 2 SP3 Planning and Implementation Guide...
Page 258: ...258 OES 2 SP3 Planning and Implementation Guide...
Page 284: ...284 OES 2 SP3 Planning and Implementation Guide...
Page 286: ...286 OES 2 SP3 Planning and Implementation Guide...
Page 294: ...294 OES 2 SP3 Planning and Implementation Guide...