9 More Discussions You Might Find Interesting
1. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
can someone provide an example, where if the parent process quits for any reason, then the child process will also close? (3 Replies)
Discussion started by: omega666
3. IP Networking
Is the last two line necessary?
struct sockaddr_in stSockAddr;
... (0 Replies)
Discussion started by: vistastar
On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization.
$ prstat -a
... (4 Replies)
Discussion started by: mahive
5. UNIX for Advanced & Expert Users
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
Discussion started by: ramen_noodle
7. UNIX and Linux Applications
I have written a socker program. I have executed that program many times without closing the socket. So I want to find which all sockets binded with which file descriptor.
Is there any way to close those socket, which have been opened in that program's execution.
please help me!.. (3 Replies)
Discussion started by: pa.chidhambaram
I have a HP-UX 11.23 that have a Server establishing connections on port 8888 .
The problem is that when i need to stop and restart the Server, the connections mantain the same state and i need to wait about 20-30 minutes before all connections finishes.
The connections remain at... (2 Replies)
Discussion started by: Renato Gregio
I have a SUN environment running an WebLogic that communicates w/a 3rd party running IIS. When the IIS site goes down (frequently), I am stuck with sockets in an ESTABLISHED state, and cannot seem to figure out how to avoid this. No exceptions are thrown as I can still open connections to the IIS... (1 Reply)
Discussion started by: teledelux
NET-SERVER(1) User Contributed Perl Documentation NET-SERVER(1)
net-server - Base Net::Server starting module
net-server [base type] [net server arguments]
net-server PreFork ipv '*'
net-server HTTP app foo.cgi
net-server HTTP app foo.cgi app /=bar.cgi
net-server HTTP port 8080 port 8443/ssl ipv '*' server_type PreFork --SSL_key_file=my.key --SSL_cert_file=my.crt access_log_file STDERR
The net-server program gives a simple way to test out code and try port connection parameters. Though the running server can be robust
enough for full tim use, it is anticipated that this binary will just be used for basic testing of net-server ports, acting as a simple
echo server, or for running development scripts as CGI.
The very first argument may be a Net::Server flavor. This is given as shorthand for writing out server_type "ServerFlavor".
Additionally, this allows types such as HTTP and PSGI, which are not true Net::Server base types, to subclass other server types via an
additional server_type argument.
net-server HTTP # becomes a HTTP server in the Fork flavor
net-server HTTP server_type PreFork # preforking HTTP server
Port to bind upon. Default is 80 if running a HTTP server as root, 8080 if running a HTTP server as non-root, or 20203 otherwise.
Multiple value can be given for binding to multiple ports. All of the methods for specifying port attributes enumerated in Net::Server
and Net::Server::Proto are available here.
net-server port 20201
net-server port 20202
net-server port 20203/IPv6
Host to bind to. Default is *. Will bind to an IPv4 socket if an IPv4 address is given. Will bind to an IPv6 socket if an IPv6
address is given (requires installation of IO::Socket::INET6).
If a hostname is given and "ipv" is still set to 4, an IPv4 socket will be created. If a hostname is given and "ipv" is set to 6, an
IPv6 socket will be created. If a hostname is given and "ipv" is set to * (default), a lookup will be performed and any available IPv4
or IPv6 addresses will be bound. The "ipv" parameter can be set directly, or passed along in the port, or additionally can be passed
as part of the hostname.
net-server host localhost
net-server host localhost/IPv4
There are many more options available. Please see the Net::Server documentation.
Paul Seamons <paul at seamons.com>
This package may be distributed under the terms of either the
GNU General Public License
Perl Artistic License
perl v5.16.2 2012-06-12 NET-SERVER(1)