Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2, Руководство администратора

Страница: 628 / 684

628 Novell ZENworks 7.3 Linux Management Administration Guide
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
Understanding the novell-zmgprebootpolicy Components
To initiate the novell-zmgprebootpolicy daemon, enter the following command (listed under Script
Location) on the Linux command line in a terminal program:
/etc/init.d/novell-zmgprebootpolicy
Table D-11 lists the arguments for this command, the executable it starts, and the configuration file it
uses:
Table D-11
Novell-zmgprebootpolicy Command Details
Configuring novell-zmgprebootpolicy
The novell-zmgprebootpolicy configuration file (
novell-zmgprebootpolicy.conf
), contains the
following parameters:
Table D-12
Novell-zmgprebootpolicy Parameters
Script Arguments: start, stop, restart, force-reload, status, showpid (for descriptions of these
arguments, see
“Understanding Script Arguments” on page 629 )
Executable: /opt/novell/zenworks/preboot/bin/novell-zmgprebootpolicyd
Configuration File: /etc/opt/novell/zenworks/preboot/novell-
zmgprebootpolicy.conf
Parameter Description
LocalInterface =
10.0.0.1 The IP address that is used by the Policy server.
This setting is intended only for use on servers with multiple LAN interfaces.
The address must be valid on the server.
By default, this parameter is commented out.
PolicyLogLevel = 1 The value assigned here determines which events are entered in novell-
zenprebootpolicy.log . Specifying a high level in an active system can
quickly fill the log. Valid values are: 0, 1, 2, 3, and 4. The default is 2.
Each message from the novell-zmgprebootpolicy server is assigned a priority
level. If
PolicyLogLevel is set to a value equal to or greater than a message’s
priority level, that message is entered in novell-zenprebootpolicy.log .
All other messages are ignored.
Priority meaning:
0: Critical information. Service start, stop, and critical events are logged.
1: Warning information. Only failed client transactions are logged.
2: Transaction information. All completed client transactions are logged.
3: Request information. All client requests are logged.
4: Debugging information. All server events, including each packet received,
are logged.
By default, this parameter is commented out.