HTML and XML content usually compresses extremely well using gzip. Most web and application servers support gzip compression. For example, Tomcat 5 supports the attribute gzip on the element.

compression=”on”
compressionMinSize=”300″
noCompressionUserAgents=”gozilla, traviata”
compressableMimeType=”text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript”

• Disable DNS lookups

You can configure your application server to perform a DNS lookup for every HTTP request. The server always know the IP address of the machine where the HTTP request originated. However, to get the name, the application server needs to send a DNS lookup query to the DNS server.

On Tomcat 5 look for the enableLookups attribute on the element and set it to false.

enableLookups=”false”

• Disable automatic deployment

Tomcat can be configured to check on a regular basis if the files of your application have changed on disk, and redeploy the application if they did. As checking if files have changed is incredibly cpu and memory intensive it is recommend to disable the automatic web application redeployment feature, on production servers which is enabled by default.

autoDeploy=”false”

Change the following log option in postgresql.conf as
log_error_verbosity = default # terse, default, or verbose messages
log_duration = on
log_line_prefix = ‘%t%d’ # Special values:
log_statement = ‘all’ # none, mod, ddl, all

Failed to run initdb: !128
Please see the logfile in ‘C:\program
Files\PostgreSQL\8.2beta1\tmp\initdb.log’.
Note! You must read/copy this logfile before yuo click OK, or it will be
automatically removed.

it is a known limitation that installation via remote desktop without /console does not work.

FIX
Use VNC or connect to RDP with Console

There are a few ways to get a console session in Windows 2000, XP, and Vista:

• Open your default.rdp file (typically in My Documents) and add the following line to the bottom: connect to console:i:1
• In the RDC window, after the address, use the switch /console
  From start, run, type: mstsc /console
• Make a shortcut to RDC, edit it, and add the /console switch to it

# pg_dump -d -O -Fp -i -x -f dump-filename.sql db-name

Backup  a Table

pg_dump -p 5432 -d -O -Fp -i -x -t TABLENAME -f DUMP-FILE.sql DBNAME

add the following two lines to the existing securityand xdmcp sections:

[security]
DisallowTCP=false
[xdmcp]
Enable=true

• Install packages:

sudo apt-get install vnc4server xinetd

• Set the VNC password

sudo vncpasswd /root/.vncpasswd

• Create a new file Xvnc to add the vnc service to xinetd:

sudo vi/etc/xinetd.d/Xvnc

• Paste these contents into the file:

service Xvnc
{
type = UNLISTED
disable = no
socket_type = stream
protocol = tcp
wait = yes
user = root
server = /usr/bin/Xvnc
server_args = -inetd :1 -query localhost -geometry 1024×768 -depth 16 -once -fp /usr/share/fonts/X11/misc -DisconnectClients=0 -NeverShared passwordFile=/root/.vncpasswd -extension XFIXES
port = 5901
}

• Reboot

UseDNS no
or
GSSAPIAuthentication no

iptables -t nat -A PREROUTING -p tcp –dport 26 -j REDIRECT –to-ports 25

Redirecting port to different host. (Redirect port 26 on 10.2.1.36 to port 25 on 10.2.1.42)

iptables -t nat -A PREROUTING -p tcp -i eth0 -d 10.2.1.36 –dport 25 -j DNAT –to 10.2.1.42:26
iptables -A FORWARD -p tcp -i eth0 -d 10.2.1.42 –dport 26 -j ACCEPT
iptables -t nat -A POSTROUTING -d 10.2.1.42 -p tcp –dport 26 -o eth0 -j MASQUERADE
iptables -A FORWARD -p tcp -i eth0 -s 10.2.1.42 –sport 26 -j ACCEPT
iptables -t nat -A POSTROUTING -p tcp -s 10.2.1.42 –sport 26 -j SNAT –to 10.2.1.36

The “-n” option prevents reading from STDIN. Redirection from /dev/null to STDIN.
“-N” tells ssh that the tunnel is not for executing remote commands.
“-T” tells ssh not to allocate a pseudo-tty on the remote system.
“-T” disables pseudo-tty allocation.

Rough diagram:
10.36.1.5:80 <— 10.36.1.6:14344

To avoid timeout:

In /etc/ssh/sshd_config on the server:

TCPKeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 99999

To enable binding address in ssh -R:

GatewayPorts yes

Man page docu for -R switch:
-R [bind_address:]port:host:hostport

Specifies that the given port on the remote (server) host is to be forwarded to the given host and port on the local side. This works by allocating a socket to listen to port on the remote side, and whenever a connection is made to this port, the connection is forwarded over the secure channel, and a connection is made to host port hostport from the local machine.

Port forwardings can also be specified in the configuration file. Privileged ports can be forwarded only when logging in as root on the remote machine. IPv6 addresses can be specified by enclosing the address in square braces or using an alternative syntax: [bind_address/]host/port/hostport.

By default, the listening socket on the server will be bound to the loopback interface only. This may be overridden by specifying a bind_address. An empty bind_address, or the address “*”, indicates that the remote socket should listen on all interfaces. Specifying a remote bind_address will only succeed if the server’s GatewayPorts option is enabled (see sshd_config(5)).

The command for ssh reverse connect tunnel :

3333 is the port that listen on Remote Host

ssh -N -R $REMOTE_PORT:localhost:22 username@3333

When somebody hits on the REMOTE_HOST:REMOTE_PORT the traffic will be forwarded to port 22 on the other end. The port 3333 will only listern on 127.0.0.1 (localhost) interface.

To bind the 3333 port to listen on all interfaces edit the sshd config (/etc/ssh/sshd_config) and enable “GatewayPorts yes” and reload sshd service or use the -g option on ssh command

Example :-
ssh -g -p 9001 -N -R 3332:localhost:8080 root@remoteip

#!/bin/sh

# $REMOTE_HOST is the name of the remote system
REMOTE_HOST=my.host.com

# $REMOTE_PORT is the remote port number that will be used to tunnel
# back to this system
REMOTE_PORT=3333

# $COMMAND is the command used to create the reverse ssh tunnel
COMMAND=”ssh -p 9001 -i “/home/cites/.ssh/id_rsa” -N -R $REMOTE_PORT:localhost:22 user_name@$REMOTE_HOST”

# Is the tunnel up? Perform two tests:

# 1. Check for relevant process ($COMMAND)
pgrep -f -x “$COMMAND” || $COMMAND

# 2. Test tunnel by looking at “netstat” output on $REMOTE_HOST
ssh $REMOTE_HOST netstat -an | egrep “tcp.*:$REMOTE_PORT.*LISTEN” \
> /dev/null 2>&1
if [ $? -ne 0 ] ; then
pkill -f -x “$COMMAND”
$COMMAND
fi

ssh -p 9001 -N -R 3332:localhost:8080 root@my.host.com

sudo apt-get install -f
sudo dpkg –configure -a
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

The first will repair any damaged packages. The second will try to re-install any missing packages. The rest will update software to the latest releases.
If you can’t repair, you need to boot with a live CD and backup all your data and then do a clean install