Difference between pages "Package:Gzip" and "Package:389 Directory Server"

(Difference between pages)
 
 
Line 1: Line 1:
 
{{Ebuild
 
{{Ebuild
|Summary=Gzip is the standard GNU compressor/decompressor, used to create and expand .gz archives.
+
|Summary=This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.
|CatPkg=app-arch/gzip
+
|CatPkg=net-nds/389-ds-base
|Maintainer=Oleg,
+
|Maintainer=Psychopatch,
|Homepage=http://www.gnu.org/software/gzip/
+
|Homepage=http://directory.fedoraproject.org/wiki/Main_Page
|Repository=Funtoo Overlay
+
|Repository=Funtoo LDAP Overlay
 
}}
 
}}
Our forked version of Gzip adds a patch to add the <tt>--rsyncable</tt> option, which creates an "rsync-friendly" archive. This option used by <tt>vzdump</tt> utility
+
This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.
  
Here is the full description of this option:
+
After emerge, to set up your LDAP server, run:
  
<blockquote>
+
<console>
"While compressing, synchronize the output occasionally based on the
+
# ##i##setup-ds.pl
input.  This reduces compression by about 1 percent most cases, but
+
</console>
means that the <tt>rsync</tt> program can take advantage of similarities
+
 
in the uncompressed input when syncronizing two files compressed with
+
If you want the Apache-based graphical admin console set up, along with your LDAP server, <tt>emerge 389-ds-admin</tt> and run:
this flag.  <tt>gunzip</tt> cannot tell the difference between a
+
 
compressed file created with this option, and one created without it."
+
<console>
</blockquote>
+
# ##i##setup-ds-admin.pl
 +
</console>
 +
 
 +
This will set up both for you, and then you will be able to remotely manage your LDAP server using the Java-based [[Package:389 Directory Server Console]].
 
{{EbuildFooter}}
 
{{EbuildFooter}}

Latest revision as of 22:43, September 18, 2014

net-nds/389-ds-base


Current Maintainer(s):Patrick Creech
Source Repository:Funtoo LDAP Overlay
Homepage

Summary: This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.


Use Flags

pam-passthru
Enable pam-passthru plugin - for simple and fast system services used in ldap
dna
Enable dna (distributed numeric assignment ) plugin - to automatically assign unique uid numbers to new user entries as they are created.
presence
Enable presence plugin - non-stabdart syntax validation
bitwise
Enable bitwise plugin - supported data in raw/bitwise format
autobind
Enable auto bind over unix domain socket (LDAPI) support
auto-dn-suffix
Enable auto bind with auto dn suffix over unix domain socket (LDAPI) support
ldapi
Enable LDAP over unix domain socket (LDAPI) support

389 Directory Server


This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.

After emerge, to set up your LDAP server, run:

# setup-ds.pl

If you want the Apache-based graphical admin console set up, along with your LDAP server, emerge 389-ds-admin and run:

# setup-ds-admin.pl

This will set up both for you, and then you will be able to remotely manage your LDAP server using the Java-based Package:389 Directory Server Console.