Fire wall Check

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Fire wall Check
# 1  
Old 01-24-2013
Fire wall Check

Is Proxy IP detectable in Firewall??? Can we monitor the Proxy IPs too?? If it is possible then explain me the procedures and How it will. . .
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. What is on Your Mind?

Up Against a Brick Wall with Cyberspace SA and Unity3D

Well, it's not working out.... ! After spending over a year coding in C# and Unity 3D creating a new way to visualize cyberspace, I recently purchased a fully maxed out 12-core CPU MacPro with 64 GB of RAM so I could gain performance by utilizing the 12-cores (24 virtual cores) waiting for Unity... (1 Reply)
Discussion started by: Neo
1 Replies

2. What is on Your Mind?

Cyber wall? just for me?

I do have a question about the great cyber wall of certain countries, like the UK for example. For years I just fetched once a week a public podcast that recently answered "notukerror", by chance I read just this weekend on slashdot about this topic. Does this mean the efforts enhanced by the EME... (4 Replies)
Discussion started by: 1in10
4 Replies

3. SuSE

Wall execution problems from cron

So I've been tasked with creating a shell script to run in a cron every few minutes to check duplex settings on my eth0 nic card. I would like for the server to send a wall message to whoever is on the console or in a terminal session. Below is what I have so far. 0,10,20,30,40,50 * * * * ... (1 Reply)
Discussion started by: lutador72
1 Replies

4. Shell Programming and Scripting

using the wall or write cmd

Hi all, i'm trying to generate a "pop up window" incorporating either the write or wall command or both. Is such a thing possible ? thanks simon2000 (2 Replies)
Discussion started by: simon2000
2 Replies

5. UNIX for Dummies Questions & Answers

wall

is there a command to send all terminals a message. i tired wall, but it only sends the message to who ever is logged in at a terminal. i need a command to send to every terminal no matter if someone is logged in or not. Thanks! -The DJ (11 Replies)
Discussion started by: djatwork
11 Replies

6. UNIX for Dummies Questions & Answers

wall and rwall commands

let's say in my office i have 20 networked sun boxes named host1 through host20. i am currently logged in as root at some random machine, which we will say host13 for this scenario's sake. now, is there any way i can send a text message of some sort over the whole network to all logged in... (1 Reply)
Discussion started by: AMisledDrummer
1 Replies

7. UNIX for Dummies Questions & Answers

wall commands

I would like to know when using the wall command can I send a message to a specific user that is logged in. Thank you (1 Reply)
Discussion started by: nascar.fan
1 Replies
Login or Register to Ask a Question
HTTP::Proxy::Engine(3pm)				User Contributed Perl Documentation				  HTTP::Proxy::Engine(3pm)

NAME
HTTP::Proxy::Engine - Generic child process manager engine for HTTP::Proxy SYNOPSIS
use HTTP::Proxy; # use the default engine for your system my $proxy = HTTP::Proxy->new(); # choose one my $proxy = HTTP::Proxy->new( engine => 'Old' ); DESCRIPTION
The HTTP::Proxy::Engine class is a front-end to actual proxy engine classes. The role of an engine is to implement the main fork+serve loop with all the required bookkeeping. This is also a good way to test various implementation and/or try out new algorithms without too much difficulties. METHODS
new() Create a new engine. The parameter "engine" is used to decide which kind of engine will be created. Other parameters are passed to the underlying engine. This method also implement the subclasses constructor (they obviously do not need the "engine" parameter). CREATING YOUR OWN ENGINE
It is possible to create one's own engine, by creating a simple subclass of HTTP::Proxy::Engine with the following methods: start() This method should handle any initialisation required when the engine starts. run() This method is the main loop of the master process. It defines how child processes are forked, checked and killed. The engine MUST have a run() method, and it will be called again and again until the proxy exits. $self->proxy->daemon returns the listening socket that can accept() connections. The child must call $self->proxy->serve_connections() on the returned socket to handle actual TCP connections. stop() This optional method should handle any cleanup procedures when the engine stops (typically when the main proxy process is killed). A subclass may also define a %defaults hash (with "our") that contains the default values for the fields used internaly. METHODS PROVIDED TO SUBCLASSES
HTTP::Proxy::Engine provides the following methods to its subclasses: proxy() Return the HTTP::Proxy object that runs the engine. max_clients() Get or set the maximum number of TCP clients, that is to say the maximum number of forked child process. Some engines may understand a value of 0 as do not fork at all. This is what HTTP::Proxy::Engine::Legacy does. make_accessors( @names ) Create accessors named after @names in the subclass package. All accessors are read/write. This is a utility method. This is a class method. AUTHOR
Philippe "BooK" Bruhat, "<book@cpan.org>". COPYRIGHT
Copyright 2005, Philippe Bruhat. LICENSE
This module is free software; you can redistribute it or modify it under the same terms as Perl itself. perl v5.12.4 2011-07-03 HTTP::Proxy::Engine(3pm)