01-10-2017
Hi Robin. These aren't database listeners. As mentioned earlier, they're gateway listeners and a listener for MSSQL has to be configured differently to one for say DRDA. They cannot be shared.
9 More Discussions You Might Find Interesting
1. Cybersecurity
/* Linux Slackware */
Nmap shows the following ports open on the gateway.
21/tcp ftp
22/tcp ssh
23/tcp telnet
25/tcp smtp
37/tcp time
80/tcp http
113/tcp auth
515/tcp printer
587/tcp submission
1024/tcp kdm
6000/tcp x11
-------------------------------
i would like to close as... (10 Replies)
Discussion started by: LowOrderBit
10 Replies
2. Shell Programming and Scripting
Hello, i need a script (bash type maybe?..), which would check open ports on 127.0.0.1 and then compare open ports with "registered/allowed" port list and try to kill the program who uses unregistered ports. It would be great that script would be started lets say every 5 or 10 minutes.
You see i... (2 Replies)
Discussion started by: MorchiuS
2 Replies
3. Shell Programming and Scripting
i'd like to grep a range of ports on a netstat -nt output, localaddress, say :1 to :1023. how do i do it via sed/awk/grep?
Thanks,
Marc (1 Reply)
Discussion started by: marcpascual
1 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I have a number of Solaris 8 Sun servers that have open ports that I cannot identify. I see some with 1012-1020 (which are reserved ports according to the IANA. Lsof does not identify these. One server has all these on and one server just has 1017.
*.1023 ... (3 Replies)
Discussion started by: csross
3 Replies
5. Solaris
Hello,
I have a number of Solaris 8 Sun servers that have open ports that I cannot identify. I see some with 1013-1023 (which are reserved ports according to the IANA. Lsof does not identify these. I rebooted the server and they went off, but this morning I saw they were all back on again. Any... (1 Reply)
Discussion started by: csgonan
1 Replies
6. Shell Programming and Scripting
My requirement is
I need to write a program in shell scripting to check 2 TCP unused unique port numbers in SOLARIS and I have to lock the same ports so that it will not be used in any other new process and the same port numbers should be used and locked in the LINUX machine to communicate... (2 Replies)
Discussion started by: sreeramr30
2 Replies
7. Solaris
hi guys,
may i know the exact steps to open a port in solaris.i have some rough idea - which is adding the port number in /etc/services.
but i am not sure the correct conventions, steps or any other steps.
kindly advise.thanks guys ! (1 Reply)
Discussion started by: cromohawk
1 Replies
8. AIX
We have a system and we have modified the /etc/ind.conf and the
/etc/services and the /etc/rc.tcpip file to turn off specific applications.
I need to know what is the correct procedure for locking down unused
ports that still appear to be in a listen mode even... (1 Reply)
Discussion started by: admaix
1 Replies
9. Shell Programming and Scripting
Hello,
I have a file with multiple columns of which the first two columns are like
a1_144601_144650 ABC_yellow_144608_16785
a1_144651_144700 ABC_yellow_144608_16785
a1_144701_144751 ABC_yellow_144608_16785
So Based on column 1 (red values) I need to check if its falling in... (3 Replies)
Discussion started by: Diya123
3 Replies
LEARN ABOUT DEBIAN
frontier::responder
Frontier::Responder(3pm) User Contributed Perl Documentation Frontier::Responder(3pm)
NAME
Frontier::Responder - Create XML-RPC listeners for normal CGI processes
SYNOPSIS
use Frontier::Responder;
my $res = Frontier::Responder->new( methods => {
add => sub{ $_[0] + $_[1] },
cat => sub{ $_[0] . $_[1] },
},
);
print $res->answer;
DESCRIPTION
Use Frontier::Responder whenever you need to create an XML-RPC listener using a standard CGI interface. To be effective, a script using
this class will often have to be put a directory from which a web server is authorized to execute CGI programs. An XML-RPC listener using
this library will be implementing the API of a particular XML-RPC application. Each remote procedure listed in the API of the user defined
application will correspond to a hash key that is defined in the "new" method of a Frontier::Responder object. This is exactly the way
Frontier::Daemon works as well. In order to process the request and get the response, the "answer" method is needed. Its return value is
XML ready for printing.
For those new to XML-RPC, here is a brief description of this protocol. XML-RPC is a way to execute functions on a different machine. Both
the client's request and listeners response are wrapped up in XML and sent over HTTP. Because the XML-RPC conversation is in XML, the
implementation languages of the server (here called a listener), and the client can be different. This can be a powerful and simple way to
have very different platforms work together without acrimony. Implicit in the use of XML-RPC is a contract or API that an XML-RPC listener
implements and an XML-RPC client calls. The API needs to list not only the various procedures that can be called, but also the XML-RPC
datatypes expected for input and output. Remember that although Perl is permissive about datatyping, other languages are not.
Unforuntately, the XML-RPC spec doesn't say how to document the API. It is recomended that the author of a Perl XML-RPC listener should at
least use POD to explain the API. This allows for the programmatic generation of a clean web page.
METHODS
new( OPTIONS )
This is the class constructor. As is traditional, it returns a blessed reference to a Frontier::Responder object. It expects arguments
to be given like a hash (Perl's named parameter mechanism). To be effective, populate the "methods" parameter with a hashref that has
API procedure names as keys and subroutine references as values. See the SYNOPSIS for a sample usage.
answer()
In order to parse the request and execute the procedure, this method must be called. It returns a XML string that contains the
procedure's response. In a typical CGI program, this string will simply be printed to STDOUT.
SEE ALSO
perl(1), Frontier::RPC2(3)
<http://www.scripting.com/frontier5/xml/code/rpc.html>
AUTHOR
Ken MacLeod <ken@bitsko.slc.ut.us> wrote the underlying RPC library.
Joe Johnston <jjohn@cs.umb.edu> wrote an adaptation of the Frontier::Daemon class to create this CGI XML-RPC listener class.
perl v5.10.1 2002-08-03 Frontier::Responder(3pm)