Mr. Uolf solve problems

Visto che sull'ultima stable la compilazione non trova gli header del kernel si fa cosi:

apt-get install open-vm-tools

Su veresioni precedenti, come squeeze, usare questa proceduta per aggiungere le fonti adatte a source-list

http://www.surlyjake.com/blog/2011/02/08/install-open-vm-tools-on-debian-6-squeeze/

passi:

aggiungere al source.list:

deb http://debian.uchicago.edu/debian/ squeeze main contrib  deb-src http://debian.uchicago.edu/debian/ squeeze main contrib

fare il canonico:

apt-get update  apt-get install open-vm-tools open-vm-source

Quasi sicuramente apparirà questo errore:

Loading open-vm-tools modules: vmhgfsFATAL: Module vmhgfs not found.  vmmemctlFATAL: Module vmmemctl not found.  vmsyncFATAL: Module vmsync not found.

perché manca un modulo, installarlo con

module-assistant auto-install open-vm -i

se non abbiamo anche una gui sulla macchina abbiamo finito, altrimenti eseguire anche:

apt-get install open-vm-toolbox

con questa app

https://play.google.com/store/apps/details?id=eu.chainfire.stickmount

less access.log | perl -p -e 's/^([0-9]*)/"[".localtime($1)."]"/e' | more

Cosi si risolve:

Fonte: http://oraclenz.wordpress.com/2012/07/19/db-controldb-console-oem-changing-hostname-or-ip-address/

attenzione che la prima istruzione è scritta male, ci vuole uno spazio tra emca e -deconfigure

$ORACLE_HOME/bin/emca  -deconfig dbcontrol db

passaggi per windows:

Setto il vecchio hostname: set ORACLE_HOSTNAME=oc-oracle-prod.com

trovo la oracle_home e ci vado dentro, poi:

bin\emca -deconfig dbcontrol db

vuole il sid del DB, rufola parecchio e a me è uscito un errore che non riusciva a cancellare una perché è bloccata directory, ma freghiamocene.

Setto il NUOVO hostname: set ORACLE_HOSTNAME=oracle-prod.com

rilancio emca:

bin\emca -config dbcontrol db -repos recreate

vuol sapere: sid, porta del db (1521 se standard) le password di SYS, DBSNP, SYSTEM, altre cose le trova da solo.

Invece di usare le partizioni si può usare un file, come su windows,

apt-get install dphys-swapfile

creare il file /etc/dphys-swapfile con dentro scritto dove deve essere creato e quanto deve essere grosso il file.

L'orrida remote console di esx 3.5 vuole l'orrido internet explorer 8versione a piacere, qui 'ho l 8) e l'orrida jre di java versione (udite udite) 1.4.2.19, scaricabile da qui:

Lo si vede da qui:

https://security.google.com/settings/security/permissions?pli=1

http://docs-legacy.fortinet.com/fos50hlp/50/index.html#page/FortiOS%205.0%20Help/HA_maintenance.085.33.html

    Downgrading cluster firmware

For various reasons you may need to downgrade the firmware that a cluster is running. You can use the information in this section to downgrade the firmware version running on a cluster.

In most cases you can downgrade the firmware on an operating cluster using the same steps as for a firmware upgrade. A warning message appears during the downgrade but the downgrade usually works and after the downgrade the cluster continues operating normally with the older firmware image.

Downgrading between some firmware versions, especially if features have changed between the two versions, may not always work without the requirement to fix configuration issues after the downgrade.

Only perform firmware downgrades during maintenance windows and make sure you back up your cluster configuration before the downgrade.

If the firmware downgrade that you are planning may not work without configuration loss or other problems, you can use the following downgrade procedure to make sure your configuration is not lost after the downgrade.

To downgrade cluster firmware

This example shows how to downgrade the cluster shown in Figure 190. The cluster consists of two cluster units (620_ha_1 and 620_ha_2). The port1 and port2 interfaces are connected networks and the port3 and port4 interfaces are connected together for the HA heartbeat.

This example, describes separating each unit from the cluster and downgrading the firmware for the standalone FortiGate units. There are several ways you could disconnect units from the cluster. This example describes using the disconnect from cluster function described in “Disconnecting a cluster unit from a cluster”.

1. Go to the System Information dashboard widget and backup the cluster configuration.

From the CLI use execute backup config.

2. Go to System > Config > HA and for 620_ha_1 select the Disconnect from cluster icon.

3. Select the port2 interface and enter an IP address and netmask of 10.11.101.101/24 and select OK.

From the CLI you can enter the following command (FG600B3908600705 is the serial number of the cluster unit) to be able to manage the standalone FortiGate unit by connecting to the port2 interface with IP address and netmask 10.11.101.101/24.

execute ha disconnect FG600B3908600705 port2 10.11.101.101/24

After 620_ha_1 is disconnected, 620_ha_2 continues processing traffic.

4. Connect to the 620_ha_1 web‑based manager or CLI using IP address 10.11.101.101/24 and follow normal procedures to downgrade standalone FortiGate unit firmware.

5. When the downgrade is complete confirm that the configuration of 620_ha_1 is correct.

6. Set the HA mode of 620_ha_2 to Standalone and follow normal procedures to downgrade standalone FortiGate unit firmware.

Network communication will be interrupted for a short time during the downgrade.

7. When the downgrade is complete confirm that the configuration of 620_ha_2 is correct.

8. Set the HA mode of 620_ha_2 to Active-Passive or the required HA mode.

9. Set the HA mode of 620_ha_1 to the same mode as 620_ha_2.