images to the Branch Server after the images are in the Administration Server’s RSYNC
directory.
IMPORTANT: RSYNC Service and LDAP Objects
The RSYNC service must be properly configured and running on the Adminis-
tration Server for the
possynimages.pl
script to run. For more information,
see Section 6.4.3, “Adding an
scServerContainer
and
scBranchServer
Object” (page 60).
Additionally, each system image has an associated
scPosImage
object in
LDAP. The object’s
scPosImageVersion
attribute should be set to active to
keep track of the most recent image version and state before
possyncimages
.pl
transfers the images to the Branch Server. For more information, see
Section 7.4.7, “Activating Images” (page 86).
The basic process is as follows:
1
The
possyncimages.pl
script initially checks via the PID file to determine
if an instance is already running.
2
The image files are then copied from the Administration Server to the Branch
Server. Boot images are copied from the
/srv/SLEPOS/boot/
directory on
the Administration Server to the
/srv/tftpboot/boot/
directory on the
Branch Server. System images and their associated MD5 checksum files are
copied from
/srv/SLEPOS/image/
to
/srv/tftpboot/image
.
During this process, the TFTP server must be stopped or otherwise prevented
from transmitting the image files to clients.
For more information on the
possyncimages.pl
script, see Section B.3.9, “pos-
syncimages.pl” (page 217).
After executing the
possyncimages.pl
script, verify the result by checking the
contents of the following directories:
•
/srv/tftpboot/image
•
/srv/tftpboot/boot
Deploying Point of Service Terminals
91
