Hi
Sorry not going to answer the question you asked but have worked on this
type of solution many times.
The problem is your redirects if a virus gets on the network it will
clobber the server as it tries to get outside. All the client MS updates
is over HTTP that will clobber it.
You need to l
For those of you who ever have this problem
Symptoms
1) Cannot connect to tomcat after a period of time
2) Heavy load on startup
3) Various strangeness with SSL certs e.g. WEB browsers reject
certs/incomplete TLS handshake
Observed case
Tomcat version we tried jakarta-tomcat-5.0.12 and jakarta-
Yes I agree 100% please ensure as we live in the age of equality to use
Subject "WILLIES" in your post.
On Fri, 2006-07-21 at 14:09 -0400, Mike Wannamaker wrote:
> I believe the subject was posted under different subject heading with no
> response and he's trying to get people looking at it, whic
Add in the follow
iptables -A INPUT -j LOG
iptables -A OUTPUT -j LOG
Then do
dmesg -c 2&> /dev/null;
Now do a shutdown then
dmesg | grep 127.0.0.1
or just
dmesg
if you are running a cluster
What ever comes out is what you are blocking on the local machine I
would suggest you do
iptables -
