Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - NETWORK DISCOVERY DATABASE STRUCTURE, System Administration Manual

Page: 240 / 374

240 ZENworks 10 Configuration Management System Administration Reference
n
ov
do
cx (e
n)
16
Ap
ril 20
10
mount -t cifs -o username= username // example.machine.com / share_name /var/opt/
novell/zenworks/content-repo/images
Or, to store bundle and policy content on another share, you can use the following command:
mount -t cifs -o username= username // example.machine.com / share_name /var/opt/
novell/zenworks/content-repo/content
28.2.2 Unmounting a Share
This mount that you created in Section 28.2.1, “Mounting a Share,” on page 239 is temporary; the
share is unmounted when the operating system is shut down or rebooted. You can also use the
following command to manually unmount the share:
umount /var/opt/novell/zenworks/content-repo
28.2.3 Creating a Permanent Mount
To ensure that the mount occurs each time the Linux server starts, you must add the following entry
to your
/etc/fstab
configuration file:
// example.machine.com / share_name /var/opt/novell/zenworks/content-repo cifs
credentials= path_to_credentials_file 0 0
The credentials file listed in the command contains a username and password. For more information,
see the
mount.cifs(8)
man page. The format of the credentials file is:
username= value
password= value
28.2.4 Moving Existing Content to the New Repository
After you change the location of a content repository by mounting a new share, any content in the
old location is no longer available. To make it available, you must move it to the new repository.
For information about ownership issues, see TID 7000673 (http://support.novell.com) .
28.3 Mounting the Content Repository on a
Linux Server to an NSS Volume
You can mount the
content-repo
directory on a Linux server on to an NSS Volume.
Before you begin, ensure that the following prerequisites are met:
Š
The NSS volume is set up and mounted in the
/media/nss/NSSVOL/
directory of the server.
Š The Samba service is installed and configured to run as
root
on the server. To verify this, run
the following command and ensure that the value in UID column is
root
, especially for the
processes with PPID = 1.
ps -Alf | grep samba