First you need to set SELinux in permissive mode (if you have enabled it) and configure the firewall to let other systems to connect to port 80/443 (HTTP and HTTPs) and 389 (LDAP server port) using the commandline tool

# system-config-securitylevel-tui

Now we need to get some more RPM repos to work:

//First the CentOS testing repo
# cd /etc/yum.repos.d/
# wget http://dev.centos.org/centos/5/CentOS-Testing.repo
//Then the RPMForge repo
# rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS//rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm
//And last the GOsa RPM repo
# cat >> GOsa.repo << EOF
> [GOsa-Repository]
> name=GOsa Repository
> baseurl=ftp://oss.gonicus.de/pub/gosa/redhat
> enabled=0
> gpgcheck=0
> EOF

As we want the system as stable as possible without many packages from externarl repositories please verify that the files CentOS-Testing.repo and rpmforge.repo both contain the line ‘enabled=0‘. Now let’s check the new repositories for new packages to install and install them:

# yum –enablerepo=rpmforge,GOsa-Repository,c5-testing check-update
//Install LDAP
# yum install openldap openldap-servers
//Install PHP 5.2 from CentOS Testing
# yum –enablerepo=c5-testing install php-common php-imap php-snmp php-mysql php-mbstring php-pdo
//Install perl-Crypt-SmbHash from RPMForge
# yum –enablerepo=rpmforge install perl-Crypt-SmbHash
//Install GOsa RPMs
# yum –enablerepo=GOsa-Repository install gosa-help-en.noarch gosa-plugin-addressbook.noarch gosa-plugin-ldapmanager.noarch gosa-plugin-mail.noarch gosa-plugin-rolemanagement.noarch gosa-plugin-systems.noarch gosa-schema.noarch gosa-plugin-goto

Now we need to be sure that Apache HTTPD and LDAP servers start at boot:

# chkconfig httpd on
# chkconfig ldap on

At this point, before configuring GOsa, you need to add specific GOsa schemas to your ldap using as reference a part of the beginning of my own /etc/openldap/slapd.conf

include         /etc/openldap/schema/core.schema
include         /etc/openldap/schema/cosine.schema
include         /etc/openldap/schema/inetorgperson.schema
include         /etc/openldap/schema/gosa/rfc2307bis.schema
include         /etc/openldap/schema/gosa/gofax.schema
include         /etc/openldap/schema/gosa/gofon.schema
include         /etc/openldap/schema/gosa/samba.schema
include         /etc/openldap/schema/gosa/gosystem.schema
include         /etc/openldap/schema/gosa/goto.schema
include         /etc/openldap/schema/gosa/samba3.schema
include         /etc/openldap/schema/gosa/gosa-samba3.schema
include         /etc/openldap/schema/gosa/goserver.schema
include         /etc/openldap/schema/gosa/goto-mime.schema
include         /etc/openldap/schema/gosa/trust.schema

Restart your openldap and finally we can connect to GOsa web interface and configure it pointing your browser at

http://<hostname>/gosa/

Now you should have a fully functional GOsa install on your CentOS5: please let me know if you found error in this tutorial or even if you found it useful.

The smartest solution I found was to use stunnel: maybe an overkill software for this simple task but it is

1. well known and opensource;
2. stable;
3. works as a windows service.

My own problem was to forward SMTP traffic from port 65025 to the well known port 25: this way if I telnet to port 65025 I can speak directly with the SMTP server listening on port 25.

The first thing was to download stunnel for windows and install it.

Now all the magic is to write the appropriate stunnel.conf file that, in my case, was something like this:

; Certificate/key is needed in server mode and optional in client mode
; The default certificate is provided only for testing and should not
; be used in a production environment
cert = stunnel.pem
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
[in65025smtp]
accept = 10.145.2.88:65025
connect = 10.145.2.88:65024
protocol = smtp
client = yes
[out25smtp]
accept = 10.145.2.88:65024
connect = 10.145.2.88:25
protocol = smtp

Looking at the stunnel.conf file provided you can see the trick: stunnel accept SMTP connections on port 65025 and encrypts them forwarding the traffic to port 65024; then it gets encrypted SMTP traffic from port 65024 and forwards it decrypted to port 25.

Last but not least is to register stunnel as service: in Windows this is as easy as 1, 2, 3

Please remember also to start the service

I hope this is clear… if you find something wrong here please let me know and I will correct it!

The first thing to do is to create the new schema (or database in MySQL world) and grant all privileges to a user (even an existing one):

create database zabbix16;
grant all privileges on zabbix16.* to zabbix@”%”;

At this point we can use the mysqldump program to dump data directly in the mysql program:

mysqldump --add-drop-table --complete-insert -uzabbix -pPWD zabbix | mysql -uzabbix -pPWD zabbix16

After some time, when mysqldump finishes, you will see the zabbix16 schema as an exact copy of the original one!

The precompiled binaries fails to run with the following message:

ld.so.1: zabbix_agentd: fatal: libresolv.so.2: version `SUNW_2.3′ not found (required by file zabbix_agentd)
ld.so.1: zabbix_agentd: fatal: libresolv.so.2: open failed: No such file or directory
Killed

Running the ldd on the zabbix_agentd will reveal the problem:

ldd /export/home/zabbix/bin/zabbix_agentd
libkvm.so.1 =>   /usr/lib/libkvm.so.1
libm.so.2 =>     /lib/libm.so.2
libresolv.so.2 =>        /lib/libresolv.so.2
libresolv.so.2 (SUNW_2.3) =>     (version not found)
libnsl.so.1 =>   /lib/libnsl.so.1
libkstat.so.1 =>         /lib/libkstat.so.1
libsocket.so.1 =>        /lib/libsocket.so.1
libc.so.1 =>     /lib/libc.so.1
libelf.so.1 =>   /lib/libelf.so.1
libmp.so.2 =>    /lib/libmp.so.2
libmd.so.1 =>    /lib/libmd.so.1
libscf.so.1 =>   /lib/libscf.so.1
libdoor.so.1 =>  /lib/libdoor.so.1
libuutil.so.1 =>         /lib/libuutil.so.1
libgen.so.1 =>   /lib/libgen.so.1

libresolv.so.2 (SUNW_2.3) is not bundled in Solaris10 but in Nevada (aka Solaris11): so the precompiled binaries were not built on Solaris10 but on Opensolaris. To overcome this problem I downloaded the Zabbix 1.4.6 sources and I compiled the agents with Sun Studio 12.

Here are my own binaries:

• Zabbix 1.4.6 Agents for Solaris 10 i386 (32bit version)
  
• Zabbix 1.4.6 Agents for Solaris 10 x64 (64bit version)
  

Use at your own risk and… enjoy!

The first thing to do is to check if you have installed the prerequisites packages:

# pkginfo -i SUNWbtool SUNWarc SUNWhea SUNWlibmr \
SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWi1of \
SUNWi1cs SUNWi15cs SUNWxwfnt SUNWpoolr SUNWpool \
SUNWuiu8

If you see any error here you must install the missing packages: if you did the “full installation” you should have all packages already installed.

Now its time to create user, groups, directories and project: as root type

//create user and groups
# groupadd oinstall
# groupadd dba
# useradd -g oinstall -G dba -m -d /export/home/oracle -s /usr/bin/bash oracle
//create the project (this is optional)
# projadd -U oracle oracle
//create the installation dir and give the right permissions
# mkdir /opt/oracle
# chown -R oracle:oinstall /opt/oracle

OK… as root we have temporarily finished!

Now log in with the oracle user and download the Oracle Client 10g for Solaris10 from Oracle website: once there you need to select the right architecture (Solaris exists for SPARC and x86 both 32 and 64 bit) and get the right archive for the Oracle client installation. In my own situation (Solaris10 on a x86 64bit) I downloaded the file called 10201_client_solx86_64.zip and I typed:

# unzip 10201_client_solx86_64.zip
# cd client/
# ./runInstaller

As you can see (click on the image to see a bigger picture) I used /opt/oracle/oraInventory and I leaved the group oinstall as the default group.

As ORACLE_HOME I used /opt/oracle/product/10.2.0/client_1.

Just before the installation finishes it prompts to you to execute two more commands as root: in my own installation I run

//execute the following commands as root
# /opt/oracle/oraInventory/orainstRoot.sh
# /opt/oracle/product/10.2.0/client_1/root.sh

but, as you may guess, your path may be different from mine.

Now, if you want to use the just installed oracle binaries, you need to change the .profile of the user adding at the end:

ORACLE_BASE=/opt/oracle
ORACLE_HOME=/opt/oracle/product/10.2.0/client_1
PATH=$PATH:/opt/oracle/product/10.2.0/client_1/bin/
export ORACLE_BASE
export ORACLE_HOME
export PATH

I hope this tutorial can help you… if you find errors please report them to me and I will correct as soon as possible.

What is a MySQL cluster?

Let’s start explaining the architecture of a MySQL cluster with an image taken from dev.mysql.com:

As you may see the MySQL cluster is an aggregation of many components:

• one management server;
• many MySQL daemons that acts as “frontend”;
• many data nodes that store the real data.

This tutorial will guide you in the creation of a cluster with:

• one management node;
• two MySQL daemons;
• two data nodes.

Obviously you can expand this configuration simply adding the components you need. As stated at the beginning of this tutorial you can create all this setup on a single server (well you need 3 IPs on the server) or, and that would be very easy, you can split the MySQL cluster components on many servers.

On the linux machine, as root, you have to run the following commands:

//create user and groups
# groupadd oinstall
# groupadd dba
# useradd -g oinstall -G dba oracle
# passwd oracle

//prepare the filesystem
# mkdir /opt/oracle
# chown -R oracle:oinstall /opt/oracle

//install some needed packages
# yum install libXp gcc make setarch libaio glibc-devel

//change /etc/redhat-release as RHEL5 is not a supported platform
# cp /etc/redhat-release /etc/redhat-release.5
# echo redhat-4 > /etc/redhat-release

OK… as root we have now finished!

Now log in with the oracle user and download the Oracle Client 10g 64bit from Oracle website: once there get the file called 10201_client_linux_x86_64.cpio.gz. Open the cpio oracle client archive and run the client installation program:

# gunzip 10201_client_linux_x86_64.cpio.gz
# cpio -idmv < 10201_client_linux_x86_64.cpio
# cd client
# ./runInstaller

I pointed the oraInventory directory to /opt/oracle in the first screen; in the second one I choose to install the Oracle 10g Client in /opt/oracle/product/10.2.0/client_1/. Just before the installation finishes it prompts to you to execute two more commands as root: in my own installation I run

//execute the following commands as root
# /opt/oracle/orainstRoot.sh
# /opt/oracle/product/10.2.0/client_1/root.sh

but, as you may guess, your path may be different from mine.

Now the final step: we have to restore the /etc/redhat-release file we changed before:

# mv /etc/redhat-release.5 /etc/redhat-release

I hope this tutorial can help you… if you find errors please report them to me and I will correct as soon as possible.

On the linux machine, as root, you have to run the following commands:

//create user and groups
# groupadd oinstall
# groupadd dba
# useradd -g oinstall -G dba oracle
# passwd oracle

//prepare the filesystem
# mkdir /opt/oracle
# chown -R oracle:oinstall /opt/oracle

//install some needed packages
# yum install libXp gcc make setarch libaio glibc-devel

//change /etc/redhat-release as RHEL5 is not a supported platform
# cp /etc/redhat-release /etc/redhat-release.5
# echo redhat-4 > /etc/redhat-release

OK… as root we have now finished!

Now log in with the oracle user and download the Oracle Client 10g from Oracle website: once there get the file called 10201_client_linux32.zip. Unzip and run the client:

# unzip 10201_client_linux32.zip
# cd client
# ./runInstaller

I pointed the oraInventory directory to /opt/oracle in the first screen; in the second one I choose to install the Oracle 10g Client in /opt/oracle/product/10.2.0/client_1/. Just before the installation finishes it prompts to you to execute two more commands as root: in my own installation I run

//execute the following commands as root
# /opt/oracle/orainstRoot.sh
# /opt/oracle/product/10.2.0/client_1/root.sh

but, as you may guess, your path may be different from mine.

Now the final step: we have to restore the /etc/redhat-release file we changed before:

# mv /etc/redhat-release.5 /etc/redhat-release

I hope this tutorial can help you… if you find errors please report them to me and I will correct as soon as possible.

Quando si parla di camorra l’immagine principale che se ne ha comunemente è quella della violenza (siano omicidi, rapimenti o estorsioni): Saviano invece stravolge questo luogo comune e svela che il vero potere del “Sistema” è quello economico prima ancora di quello militare.

Partendo esclusivamente da atti di cronaca e da indagini della magistratura (che talvolta divengono elenchi lunghissimi di nomi, luoghi e date) Saviano divide “il Sistema” in parti per poterlo esaminare in modo più analitico: si va da una divisione territoriale (Napoli, periferia di Napoli, Caserta) ad una divisione basata sulle varie specializzazione delle famiglie camorristiche (droga, rifiuti, edilizia, etc.). In questo modo l’autore riesce a mostrare l’infinita complessità e le numerose ramificazioni che “il Sistema” ha sviluppato nel corso degli anni: fa spesso impressione leggere che la tal famiglia ha interessi in Veneto o in Lombardia, che la tal altra smaltisce rifiuti pericolosi in Molise e non più solo nella martoriata Campania.

Ovviamente, anche per Saviano, la camorra non si riduce ad un semplice impero economico: “il Sistema” ha una sua base nella violenza e nella potenza militare. Un intero capitolo è dedicato alla guerra di Secondigliano: tra il 2004 e il 2005 ci furono diverse decine di morti ammazzati a causa di una lotta di potere tra il clan Di Lauro e “gli Scissionisti”. In un sistema dove l’ordine delle cose è dettato dalla ricchezza economica e dal potere militare sono all’ordine del giorno che i tentativi di scalata al potere: “gli Scissionisti”, che erano persone affiliate al clan Di Lauro, cercarono di staccarsi e di poter gestire in autonomia i traffici che gestivano originariamente per i Di Lauro. Tutti ricordiamo le notizie da Napoli di quel periodo e Saviano riporta tutte le morti causate da questa guerra intestina al clan Di Lauro: da giornalista come è, in stretto ordine cronologico, Saviano fa la cronaca di tutti gli avvenimenti di quel periodo a partire dai motivi della “scissione”, passando per le decine di morti, per arrivare alla fine alla pace imposta dalle altre componenti del “Sistema” ormai stufe delle luci della ribalta che avevano illuminato la periferia di Napoli in quel periodo.

“Il Sistema” vive e prolifica nel silenzio, senza riflettori puntati addosso: è questo il punto fondamentale del libro di Saviano. Solo parlando della camorra, solo rendendo pubblico quello che avviene in quelle zone (e ormai in tutta Italia) si riesce a fare il danno maggiore al “Sistema”: la pubblicità è quello che il sistema cerca sempre ed in ogni modo di evitare. Parlare del “Sistema” è il primo tassello, il più “semplice” ma anche efficace, per intaccare questi poteri distorti e contorti che avvelenano la vita della Campania e dell’Italia tutta.

Voto: 8/10

P.S.: Gomorra non è un romanzo. E’ la cruda realtà di una situazione orribile che stiamo vivendo. Non è un libro da leggere per piacere: se io fossi un insegnante di una scuola superiore obbligherei i miei studenti a leggerlo. Sapere è il primo modo per capire e cercare di cambiare le cose.

The  first thing is to get the HP-UX PA-RISC install server CDs from HP website:if you do not have the original CDs you can get them as trial from here.

Now its time to install the Disk Agent on the server you need to backup; you need to install a package that is not installed by default on the Ubuntu Linux 7.04: inetd. So, as “administrator”, execute the command:

> sudo apt-get install netkit-inetd

to get the needed package installed.

Insert the first CD of the HP-UX PA-RISC install server on the optical drive of the server and mount it:

> mount /dev/hda /mnt

Now it is install time:

> cd /mnt/LOCAL_INSTALL
> ./omnisetup.sh

Answer all the questions the installer asks to you and finish the installation. In my installation the Data Protector agent was correctly added to the inetd configuration:

> cat /etc/inetd.conf
omni stream tcp nowait root /opt/omni/lbin/inet inet -log /var/opt/omni/log/inet.log

OK… we are at the end…

> /etc/init.d/inetd restart

and now try if the Data Protector agent answers to port 5555:

> telnet localhost 5555

That’s all… if you encounter any problem leave a comment here… I’ll try to help you.

Leave a comment even if you have a smarter method… I am very glad to learn.