[csw-devel] SF.net SVN: gar:[17666] csw/mgar/pkg/opencsw-manual/trunk/files/ for-administrators
wahwah at users.sourceforge.net
wahwah at users.sourceforge.net
Sat Apr 14 13:33:07 CEST 2012
Revision: 17666
http://gar.svn.sourceforge.net/gar/?rev=17666&view=rev
Author: wahwah
Date: 2012-04-14 11:33:07 +0000 (Sat, 14 Apr 2012)
Log Message:
-----------
manual: Line wraps to 80 columns
Modified Paths:
--------------
csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/configuring-services.rst
csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/getting-started.rst
Modified: csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/configuring-services.rst
===================================================================
--- csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/configuring-services.rst 2012-04-14 11:32:45 UTC (rev 17665)
+++ csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/configuring-services.rst 2012-04-14 11:33:07 UTC (rev 17666)
@@ -5,35 +5,27 @@
/etc/opt/csw vs. /opt/csw/etc
=============================
-There are two locations where configuration files are stored. This may look confusing at first,
-the reason is that we try to support both sparse zones and full zones as good as possible.
-Remember that in a sparse root environment `/opt` is shared from the global zone. As a rule
-of thumb configuration files which are specific to a zone are kept in `/etc/opt/csw` which is
-also generally preferred (these are in fact most of the configuration files), whereas
-`/opt/csw/etc` is used for configuration files which are globally set. Some packages honour
-both locations, where the global `/opt/csw/etc` is read first and can be customized by
-`/etc/opt/csw`, but this is specific to the package as not all upstream software allows
-this easily.
+There are two locations where configuration files are stored. This may look
+confusing at first, the reason is that we try to support both sparse zones and
+full zones as good as possible. Remember that in a sparse root environment
+`/opt` is shared from the global zone. As a rule of thumb configuration files
+which are specific to a zone are kept in `/etc/opt/csw` which is also generally
+preferred (these are in fact most of the configuration files), whereas
+`/opt/csw/etc` is used for configuration files which are globally set. Some
+packages honour both locations, where the global `/opt/csw/etc` is read first
+and can be customized by `/etc/opt/csw`, but this is specific to the package as
+not all upstream software allows this easily.
-There are some exceptions like Apache, where the configuration files are historically in
-`/opt/csw/apache2/etc`, but these are likely to go away some time.
+There are some exceptions like Apache, where the configuration files are
+historically in `/opt/csw/apache2/etc`, but these are likely to go away some
+time.
preserveconf
============
-Configuration files are usually shipped as template with a `.CSW` suffix which is copied during installation
-to the native name without the suffix. This file is meant to be user-adjustable. On package
-deinstallation or update the template is deinstalled whereas the configuration file without suffix
-is kept unless it hasn't been modified.
-
-
-RC/SMF
-======
-
-...
-
-csw.conf
-========
-
-...
+Configuration files are usually shipped as template with a `.CSW` suffix which
+is copied during installation to the native name without the suffix. This file
+is meant to be user-adjustable. On package deinstallation or update the
+template is deinstalled whereas the configuration file without suffix is kept
+unless it hasn't been modified.
Modified: csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/getting-started.rst
===================================================================
--- csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/getting-started.rst 2012-04-14 11:32:45 UTC (rev 17665)
+++ csw/mgar/pkg/opencsw-manual/trunk/files/for-administrators/getting-started.rst 2012-04-14 11:33:07 UTC (rev 17666)
@@ -47,8 +47,8 @@
------------------
Now that you are about to install lots of stuff it may be a good time to select
-one of the mirrors from ``mirror.opencsw.org`` close to you. The official mirrors
-are listed at::
+one of the mirrors from ``mirror.opencsw.org`` close to you. The official
+mirrors are listed at::
http://www.opencsw.org/get-it/mirrors/
@@ -57,13 +57,14 @@
- ``/etc/opt/csw/pkgutil.conf``
- ``/opt/csw/etc/pkgutil.conf``
-This may seem confusing, the reason why there are two is that it is possible to run
-OpenCSW in a `sparse root environment`_ where ``/opt`` is not writable. In this scenario
-you use configurations in ``/opt/csw/etc`` for global settings and ``/etc/opt/csw``
-for zone-specific setting. Both ``pkgutil.conf`` are identical on installation with all
-configuration options commented out, so you can just pick one for now. As a rule of thumb it is
-recommended to prefer the more prominent ``/etc/opt/csw``. Please uncomment the line
-with ``mirror`` so it looks similar to this with the URL replaced by the mirror you picked::
+This may seem confusing, the reason why there are two is that it is possible to
+run OpenCSW in a `sparse root environment`_ where ``/opt`` is not writable. In
+this scenario you use configurations in ``/opt/csw/etc`` for global settings
+and ``/etc/opt/csw`` for zone-specific setting. Both ``pkgutil.conf`` are
+identical on installation with all configuration options commented out, so you
+can just pick one for now. As a rule of thumb it is recommended to prefer the
+more prominent ``/etc/opt/csw``. Please uncomment the line with ``mirror`` so
+it looks similar to this with the URL replaced by the mirror you picked::
mirror=http://mirror.opencsw.org/opencsw/unstable
@@ -83,10 +84,11 @@
Setting up cryptographic verification
-------------------------------------
-The catalog is signed with PGP and it is a good idea to set up your system to verify
-the integrity of the catalog. As the catalog itself contains hashes for all packages
-in the catalog this ensures you actually install the packages which were officially
-released. First you need to install ``pgp`` (of course with pkgutil!)::
+The catalog is signed with PGP and it is a good idea to set up your system to
+verify the integrity of the catalog. As the catalog itself contains hashes for
+all packages in the catalog this ensures you actually install the packages
+which were officially released. First you need to install ``pgp`` (of course
+with pkgutil!)::
pkgutil -y -i gpg
@@ -159,29 +161,31 @@
Setting up a private mirror
---------------------------
-Sometimes it is sufficient to just go on with a mirror on the internet. However, there are situations
-where a local mirror can be useful. When you have a lot of servers accessing the repository, want to control
-the package updates exactly or when your production servers just can't access the internet at all
-a local mirror is necessary.
+Sometimes it is sufficient to just go on with a mirror on the internet.
+However, there are situations where a local mirror can be useful. When you have
+a lot of servers accessing the repository, want to control the package updates
+exactly or when your production servers just can't access the internet at all a
+local mirror is necessary.
-To set up the mirror you should use rsync as it can update your local copy quickly and with low
-bandwidth use and also preserves hardlinks. Not all mirrors provide access via the rsync protocol,
-a list can be found at http://www.opencsw.org/get-it/mirrors/ .
-To make a full copy of the OpenCSW repository use this::
+To set up the mirror you should use rsync as it can update your local copy
+quickly and with low bandwidth use and also preserves hardlinks. Not all
+mirrors provide access via the rsync protocol, a list can be found at
+http://www.opencsw.org/get-it/mirrors/ . To make a full copy of the OpenCSW
+repository use this::
pkgutil -y -i rsync
rsync -aH --delete rsync://rsync.opencsw.org/opencsw /my/server/repo
-The directory ``repo`` can either be shared via HTTP or via NFS to the pkgutil clients.
-Use http://myserver/url-to-repo/ for HTTP and file:///myserver/dir-to-repo for NFS as
-mirror option in pkgutil.
+The directory ``repo`` can either be shared via HTTP or via NFS to the pkgutil
+clients. Use http://myserver/url-to-repo/ for HTTP and
+file:///myserver/dir-to-repo for NFS as mirror option in pkgutil.
Mirroring only a subset
=======================
-You can also mirror only a subset of the repository, e.g. the 'unstable' catalog or even
-just a few packages.
+You can also mirror only a subset of the repository, e.g. the 'unstable'
+catalog or even just a few packages.
pkgutil --stream
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
More information about the devel
mailing list