Our product historically used an Oracle backend, and after implementing simple date based range partitioning we got 20-30 time performance increase in our queries. We had used MySQL in other more minor products we had developed, but we couldn't move to it until partitioning was implemented. In Dec 05 we started to test MySQL partitioning, where partitioning syntax was supported but the optimisations were not in place. As soon as the optimisations we put in, we were able to run a side by side comparison against unpartitioned tables and Oracle partitions. Not only did we get in MySQL a 30+ times performance increase, but the MySQL version ran nearly twice as fast as the same Oracle configuration in a like for like test.
Hello,
we got a high security network which is completely offline.
We want to use a Sync Host like described here in the Redhat documentation for Sattelite 6.
I have the following Questions:
- We need the complete Repository not only the main one how much space we need for this ?
- Can... (2 Replies)
Can anyone point me towards a list that shows which Satellite versions roughly align with which Spacewalk versions, in terms of functionality?
Thanks in advance,
Akbar. (2 Replies)
Hi all,
We have been using Satellite to patch our RedHat servers for a while but up until recently these have only been virtual machines. Now we have a requirement to install a few physicals and I am trying to setup a sync a custom channel for the HP reository.
Our setup is that the... (2 Replies)
I am getting ready to install RHEL6 server. I have to create these partitions:
/ 10GB
SWAP 3GB
/opt/kent 10GB
/opt/kent/logs
/backup 20 GB
Will Gparted do this? or whats the easiest way? or even a tutorial?I am so new to this (4 Replies)
Ten movies have been nominated as best motion picture by the International Press Academy, presentation of the 2012 Satellite Awards will be held on 16th December at Los Angeles, CA.
Place your bits here on one of the below nominated movie of your choice:-
Argo
... (0 Replies)
Wild shot in the dark as both are exactly ubiquitous technologies, but here it goes: Anybody have any experience using a Dell KACE to PXE boot to a Red Hat Satellite kickstart install? I've set up the kickstart by itself before but I'm not sure there's a way to configure the KACE so that it will... (0 Replies)
Hi,
I'd like to know more about RHN and their RHN PROXY.
- If I will buy PROXY, do I need to get licenses for all my RHELs to have them updated? What are benefits of proxy?
- If I will buy (doubt it) Satellite, will I be able to connect all my boxes to Satellite and have them upgraded... (5 Replies)
Hi folks,
Ubuntu 10.04-1 64-bit
HD - 1T SATA3
I ran graphic installation installing Ubuntu-10.04-1 desktop from Live CD
The partition on the new HD is as follow;
/root
/home
/kvm
(kvm is for keeping the guests of KVM, the virtualizer)
Installion went through without problem abd... (0 Replies)
Hi all,
I have a bit of an inexplicable problem....
Up until today, on my Toshiba Satellite A30 Laptop running SuSE 8.2 Professional, I had a dual mouse (USB Mouse / Touchpad) configuration in X and everything was running fine.
I booted the laptop today, and for some reason unbeknownst to... (3 Replies)
SLAPD.BACKENDS(5) File Formats Manual SLAPD.BACKENDS(5)NAME
slapd.backends - backends for slapd, the stand-alone LDAP daemon
DESCRIPTION
The slapd(8) daemon can use a variety of different backends for serving LDAP requests. Backends may be compiled statically into slapd, or
when module support is enabled, they may be dynamically loaded. Multiple instances of a backend can be configured, to serve separate data-
bases from the same slapd server.
Configuration options for each backend are documented separately in the corresponding slapd-<backend>(5) manual pages.
bdb This was the recommended primary backend through OpenLDAP 2.3, but it has since been superseded by the hdb backend. It takes care
to configure it properly. It uses the transactional database interface of the Oracle Berkeley DB (BDB) package to store data.
config This backend is used to manage the configuration of slapd at run-time. Unlike other backends, only a single instance of the config
backend may be defined. It also instantiates itself automatically, so it is always present even if not explicitly defined in the
slapd.conf(5) file.
dnssrv This backend is experimental. It serves up referrals based upon SRV resource records held in the Domain Name System.
hdb This is the recommended primary backend for a normal slapd database. hdb is a variant of the bdb backend that uses a hierarchical
database layout. This layout stores entry DNs more efficiently than the bdb backend, using less space and requiring less work to
create, delete, and rename entries. It is also one of the few backends to support subtree renames.
ldap This backend acts as a proxy to forward incoming requests to another LDAP server.
ldif This database uses the filesystem to build the tree structure of the database, using plain ascii files to store data. Its usage
should be limited to very simple databases, where performance is not a requirement. This backend also supports subtree renames.
mdb This will soon be the recommended primary backend, superseding hdb. This backend uses OpenLDAP's own MDB transactional database
library. It is extremely compact and extremely efficient, delivering much higher performance than the Berkeley DB backends while
using significantly less memory. Also, unlike Berkeley DB, MDB is crash proof, and requires no special tuning or maintenance. This
backend also supports subtree renames.
meta This backend performs basic LDAP proxying with respect to a set of remote LDAP servers. It is an enhancement of the ldap backend.
monitor
This backend provides information about the running status of the slapd daemon. Only a single instance of the monitor backend may be
defined.
ndb This backend is experimental. It uses the transactional database interface of the MySQL Cluster Engine (NDB) to store data. Note
that Oracle, which now owns MySQL, has withdrawn support for NDB and this backend is unlikely to be developed any further.
null Operations in this backend succeed but do nothing.
passwd This backend is provided for demonstration purposes only. It serves up user account information from the system passwd(5) file.
perl This backend embeds a perl(1) interpreter into slapd. It runs Perl subroutines to implement LDAP operations.
relay This backend is experimental. It redirects LDAP operations to another database in the same server, based on the naming context of
the request. Its use requires the rwm overlay (see slapo-rwm(5) for details) to rewrite the naming context of the request. It is
primarily intended to implement virtual views on databases that actually store data.
shell This backend executes external programs to implement LDAP operations. It is primarily intended to be used in prototypes.
sql This backend is experimental. It services LDAP requests from an SQL database.
FILES
/etc/openldap/slapd.conf
default slapd configuration file
/etc/openldap/slapd.d
default slapd configuration directory
SEE ALSO ldap(3), slapd-bdb(5), slapd-config(5), slapd-dnssrv(5), slapd-hdb(5), slapd-ldap(5), slapd-ldif(5), slapd-mdb(5), slapd-meta(5),
slapd-monitor(5), slapd-ndb(5), slapd-null(5), slapd-passwd(5), slapd-perl(5), slapd-relay(5), slapd-shell(5), slapd-sql(5), slapd.conf(5),
slapd.overlays(5), slapd(8). "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
ACKNOWLEDGEMENTS
OpenLDAP Software is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>. OpenLDAP Software is derived from Uni-
versity of Michigan LDAP 3.3 Release.
OpenLDAP 2.4.39 2014/01/26 SLAPD.BACKENDS(5)