Red Hat NETWORK SATELLITE SERVER 4.1.0, Руководство по установке

Страница: 72 / 80

68 Chapter 8. Maintenance
This opens the crontab in a text editor, by default Vi. Another editor can be used by first
changing the
EDITOR
variable, like so:
export EDITOR=gedit
.
Once opened, use the first five fields (minute, hour, day, month, and weekday) to sched-
ule the synchronization. Remember, hours use military time. Edit the crontab to include
random synchronization, like so:
0 1 * * * perl -le ’sleep rand 9000’ && satellite-sync --email >/dev/null \
2>/dev/null
This particular job will run randomly between 1:00 a.m. and 3:30 a.m. system time each
night and redirect
stdout
and
stderr
from
cron
to prevent duplicating the more easily
read message from
satellite-sync
. Options other than
--email
can also be included.
Refer to Table 6-2 for the full list of options. Once you exit from the editor, the modified
crontab is installed immediately.
8.9. Implementing PAM Authentication
As security measures become increasingly complex, administrators must be given tools
that simplify their management. For this reason, RHN Satellite Server supports network-
based authentication systems via Pluggable Authentication Modules (PAM). PAM is a suite
of libraries that helps system administrators integrate the Satellite with a centralized au-
thentication mechanism, thus eliminating the need for remembering multiple passwords.
RHN Satellite Server supports LDAP, Kerberos, and other network-based authentication
systems via PAM. To enable the Satellite to use PAM and your organization’s authentica-
tion infrastructure, complete the following tasks.
Set up a PAM service file (usually
/etc/pam.d/rhn-satellite
) and have the Satellite
use it by adding the following line to
/etc/rhn/rhn.conf
:
pam_auth_service = rhn-satellite
This assumes the PAM service file is named
rhn-satellite
.
To enable a user to authenticate against PAM, select the checkbox labeled Pluggable Au-
thentication Modules (PAM) . It is positioned below the password and password confir-
mation fields on the Create User page.
As an example, to authenticate against Kerberos one could put the following in
/etc/pam.d/rhn-satellite
:
#%PAM-1.0
auth required /lib/security/pam_env.so
auth sufficient /lib/security/pam_krb5.so no_user_check
auth required /lib/security/pam_deny.so
account required /lib/security/pam_krb5.so no_user_check