Build an exactly similar ubuntu installation on another computer.
Run
$ dpkg --get-selections >my_pakages
on the machine that you want to clone.
Install a clean copy of Ubuntu on the target machine.
Copy the file my_packages to the target machine.
Run the following command on the target machine.
$ sudo dpkg --set-selections < ./package_names
$ sudo apt-get -u dselect-upgrade
Custom Search
Wednesday, December 14, 2011
ldap CentOS6 Configuration
ldap Centos 6 Configuration
======== 1 ==========
# yum install ldap-servers ldap-clients
copy slapd.conf from the old to the new server
# scp -p rhel5server:/etc/openldap/slapd.conf /etc/openldap
edit /etc/sysconfig/ldap if you want to change settings
# vi /etc/sysconfig/ldap
adapt slapd.conf to the new servername and possibly cert and key locations
# vi /etc/openldap/slapd.conf
Disable the whole cn=config mess
# mv /etc/openldap/slapd.d /etc/openldap.slapd.d.org
start the server
# service slapd restart
========== 2 ==========
----------------------- /etc/openldap/slapd.conf
database bdb
suffix "o=localhost.localdomain"
rootdn "cn=Manager,o=localhost.localdomain"
rootpw secret
------------------------- root.ldif
dn: o=localhost.localdomain
objectclass: dcobject
objectClass: organization
o: localhost.localdomain
dc: localhost
-------------------------- add user
[saju@localhost Desktop]$ ldapadd -x -D 'cn=Manager,o=localhost.localdomain' -W -f root.ldif
Enter LDAP Password:
adding new entry "o=localhost.localdomain"
----------------------------
====== 3 ====== /etc/openldap/slapd.conf
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
pidfile /var/run/openldap/slapd.pid
argsfile /var/run/openldap/slapd.args
# Load dynamic backend modules:
# modulepath /usr/lib/openldap
# Modules available in openldap-servers-overlays RPM package
# Module syncprov.la is now statically linked with slapd and there
# is no need to load it here
# moduleload accesslog.la
# moduleload auditlog.la
# moduleload denyop.la
# moduleload dyngroup.la
# moduleload dynlist.la
# moduleload lastmod.la
# moduleload pcache.la
# moduleload ppolicy.la
# moduleload refint.la
# moduleload retcode.la
# moduleload rwm.la
# moduleload smbk5pwd.la
# moduleload translucent.la
# moduleload unique.la
# moduleload valsort.la
# modules available in openldap-servers-sql RPM package:
# moduleload back_sql.la
# The next three lines allow use of TLS for encrypting connections using a
# dummy test certificate which you can generate by changing to
# /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it. Your client software
# may balk at self-signed certificates, however.
# TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
# TLSCertificateFile /etc/pki/tls/certs/slapd.pem
# TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem
# Sample security restrictions
# Require integrity protection (prevent hijacking)
# Require 112-bit (3DES or better) encryption for updates
# Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64
# Sample access control policy:
# Root DSE: allow anyone to read it
# Subschema (sub)entry DSE: allow anyone to read it
# Other DSEs:
# Allow self write access
# Allow authenticated users read access
# Allow anonymous users to authenticate
# Directives needed to implement policy:
# access to dn.base="" by * read
# access to dn.base="cn=Subschema" by * read
# access to *
# by self write
# by users read
# by anonymous auth
#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn. (e.g., "access to * by * read")
#
# rootdn can always read and write EVERYTHING!
#######################################################################
# ldbm and/or bdb database definitions
#######################################################################
database bdb
suffix "o=localhost.localdomain"
rootdn "cn=Manager,o=localhost.localdomain"
rootpw secret
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
# rootpw secret
# rootpw {crypt}ijFYNcSNctBYg
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /var/lib/ldap
# Indices to maintain for this database
index objectClass eq,pres
index ou,cn,mail,surname,givenname eq,pres,sub
index uidNumber,gidNumber,loginShell eq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntry eq,pres,sub
# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
#replica host=ldap-1.example.com:389 starttls=critical
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/ldap-master.example.com@EXAMPLE.COM
======== 1 ==========
# yum install ldap-servers ldap-clients
copy slapd.conf from the old to the new server
# scp -p rhel5server:/etc/openldap/slapd.conf /etc/openldap
edit /etc/sysconfig/ldap if you want to change settings
# vi /etc/sysconfig/ldap
adapt slapd.conf to the new servername and possibly cert and key locations
# vi /etc/openldap/slapd.conf
Disable the whole cn=config mess
# mv /etc/openldap/slapd.d /etc/openldap.slapd.d.org
start the server
# service slapd restart
========== 2 ==========
----------------------- /etc/openldap/slapd.conf
database bdb
suffix "o=localhost.localdomain"
rootdn "cn=Manager,o=localhost.localdomain"
rootpw secret
------------------------- root.ldif
dn: o=localhost.localdomain
objectclass: dcobject
objectClass: organization
o: localhost.localdomain
dc: localhost
-------------------------- add user
[saju@localhost Desktop]$ ldapadd -x -D 'cn=Manager,o=localhost.localdomain' -W -f root.ldif
Enter LDAP Password:
adding new entry "o=localhost.localdomain"
----------------------------
====== 3 ====== /etc/openldap/slapd.conf
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
pidfile /var/run/openldap/slapd.pid
argsfile /var/run/openldap/slapd.args
# Load dynamic backend modules:
# modulepath /usr/lib/openldap
# Modules available in openldap-servers-overlays RPM package
# Module syncprov.la is now statically linked with slapd and there
# is no need to load it here
# moduleload accesslog.la
# moduleload auditlog.la
# moduleload denyop.la
# moduleload dyngroup.la
# moduleload dynlist.la
# moduleload lastmod.la
# moduleload pcache.la
# moduleload ppolicy.la
# moduleload refint.la
# moduleload retcode.la
# moduleload rwm.la
# moduleload smbk5pwd.la
# moduleload translucent.la
# moduleload unique.la
# moduleload valsort.la
# modules available in openldap-servers-sql RPM package:
# moduleload back_sql.la
# The next three lines allow use of TLS for encrypting connections using a
# dummy test certificate which you can generate by changing to
# /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it. Your client software
# may balk at self-signed certificates, however.
# TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
# TLSCertificateFile /etc/pki/tls/certs/slapd.pem
# TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem
# Sample security restrictions
# Require integrity protection (prevent hijacking)
# Require 112-bit (3DES or better) encryption for updates
# Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64
# Sample access control policy:
# Root DSE: allow anyone to read it
# Subschema (sub)entry DSE: allow anyone to read it
# Other DSEs:
# Allow self write access
# Allow authenticated users read access
# Allow anonymous users to authenticate
# Directives needed to implement policy:
# access to dn.base="" by * read
# access to dn.base="cn=Subschema" by * read
# access to *
# by self write
# by users read
# by anonymous auth
#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn. (e.g., "access to * by * read")
#
# rootdn can always read and write EVERYTHING!
#######################################################################
# ldbm and/or bdb database definitions
#######################################################################
database bdb
suffix "o=localhost.localdomain"
rootdn "cn=Manager,o=localhost.localdomain"
rootpw secret
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
# rootpw secret
# rootpw {crypt}ijFYNcSNctBYg
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /var/lib/ldap
# Indices to maintain for this database
index objectClass eq,pres
index ou,cn,mail,surname,givenname eq,pres,sub
index uidNumber,gidNumber,loginShell eq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntry eq,pres,sub
# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
#replica host=ldap-1.example.com:389 starttls=critical
# bindmethod=sasl saslmech=GSSAPI
# authcId=host/ldap-master.example.com@EXAMPLE.COM
how to install new software in Centos
how to install new software in Centos
1. Download the latest rpmforge-release rpm from
http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/
2. Install rpmforge-release rpm:
# rpm -Uvh rpmforge-release*rpm
Example:
# wget http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
# rpm -Uvh rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
3. Install gq rpm package (Install new software):
# yum install gq
1. Download the latest rpmforge-release rpm from
http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/
2. Install rpmforge-release rpm:
# rpm -Uvh rpmforge-release*rpm
Example:
# wget http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
# rpm -Uvh rpmforge-release-0.5.2-2.el5.rf.x86_64.rpm
3. Install gq rpm package (Install new software):
# yum install gq
Monday, December 12, 2011
How to draw inheritance diagram using sphinx
How to draw inheritance diagram using sphinx
Add line "sphinx.ext.inheritance_diagram" to your conf.py - extensions.
Add directive "inheritance-diagram" into your *.rst file.
More...
Add line "sphinx.ext.inheritance_diagram" to your conf.py - extensions.
Add directive "inheritance-diagram" into your *.rst file.
More...
complete documentation python project using sphinx 2 steps
how to create complete documentation for python project using sphinx quickly 2 steps
Create a folder named "doc" inside your project directory.
$cd doc
$sphinx-apidoc -f -F -o . /home/saju/your_project_dir
$make html
Create a folder named "doc" inside your project directory.
$cd doc
$sphinx-apidoc -f -F -o . /home/saju/your_project_dir
$make html
Subscribe to:
Posts (Atom)