ghm1014's questions

I'm trying to export LDAP data from a Zimbra schema into a basic OpenLDAP schema. Obviously the Zimbra schema has much more attributes than the basic OpenLDAP. My question is if there is a way of:

• Either export the LDAP data filtering only attributes present on the basic OpenLDAP schema
• Or having a full export of the LDAP data with Zimbra attributes, somehow import only the valid attributes
• Or if there is a tool to modify the LDIF file to remove the attributes not present in the basic OpenLDAP schema

The LDAP has a few hundred of nodes, so I was looking for a way to make this at least semi-automatically

I have several environments of the same application in different servers. The directory structure is very similar, so I'd like to use one single FileSet for all of them. For example:

- server1: /opt/env1/app/logs
- server1: /opt/env1/app/bin
- server1: /opt/env1/app/temp
- server1: /opt/env1/app/lib

- server2: /opt/env2/app/logs
- server2: /opt/env2/app/bin
- server2: /opt/env2/app/temp
- server2: /opt/env2/app/lib

- server2: /opt/env3/app/logs
- server2: /opt/env3/app/bin
- server2: /opt/env3/app/temp
- server2: /opt/env3/app/lib

I'd like to have something like:

FileSet {
  Name = "APP"
  Include {
    Options {
      signature = MD5
      Compression = GZIP
    }
    File = "/opt/${env}/app"
  }
  Exclude {
    File = "/opt/${env}/app/logs"
    File = "/opt/${env}/app/temp"
  }
}

Then:

Job {
  Name = "JOBENV1"
  #somehow set env variable as env1
  FileSet="APP"
  ...
}

Job {
  Name = "JOBENV2"
  #somehow set env variable as env2
  FileSet="APP"
  ...
}

Job {
  Name = "JOBENV3"
  #somehow set env variable as env3
  FileSet="APP"
  ...
}

I have a server with several disks and partitions. For an specific disk I want to know if it is local or in the SAN.

I ran some commands:

[root@server]# ls -l /sys/block/*/device
lrwxrwxrwx  1 root root 0 Jul 22 12:15 /sys/block/hda/device -> ../../devices/pci0000:00/0000:00:1f.1/ide0/0.0
lrwxrwxrwx  1 root root 0 Jul 22 12:15 /sys/block/sda/device -> ../../devices/pci0000:00/0000:00:03.0/0000:01:00.0/0000:02:0e.0/host0/target0:2:0/0:2:0:0
lrwxrwxrwx  1 root root 0 Jul 22 12:15 /sys/block/sdb/device -> ../../devices/pci0000:00/0000:00:03.0/0000:01:00.0/0000:02:0e.0/host0/target0:2:1/0:2:1:0
lrwxrwxrwx  1 root root 0 Jul 22 12:15 /sys/block/sdc/device -> ../../devices/platform/host3/target3:0:0/3:0:0:0

How can I certainly know which device is local and which is connected to the SAN?

I'd like to enable jmxremote to monitor Apache Tomcat resources utilization with Munin, but I want to know if this will affect the servers performance, is so, how much will it be impacted.