Sponsored Content
Top Forums Programming tcp server listening, client connecting problems Post 302176616 by odys on Tuesday 18th of March 2008 06:59:16 PM
Old 03-18-2008
Dont you need a loop with read() after accept()?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Perl Script Listening On A TCP Port

Hi, Im programming a perl script which will act as a daemon listening on a tcp port (2323) and will take (<stdin>) from the client (im going to use telnet) and run the arguments from (<stdin>) against an program already on the server, which is used to list books in the library at uni. So far... (1 Reply)
Discussion started by: emcb
1 Replies

2. UNIX for Dummies Questions & Answers

TCP Listening Ports

Hello all, Can someone instruct me on how to change the listening port for ftp ( or any tcp service) from 21 to another port number? Thanks in advance.. -AJ (3 Replies)
Discussion started by: jacobsa
3 Replies

3. Linux

NFS Server FC7 Solaris client problems!

Hi, my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client. I always got the messages no permission. Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Discussion started by: joerg
3 Replies

4. UNIX for Dummies Questions & Answers

Help connecting to linux server from shh client in windows!

I just installed the latest version of unbuntu server and want to connect from windows using a ssh client. This is my first linux server, so bare with me =) For my server... cat /etc/hostsgives me 127.0.0.1 localhost 127.0.1.1 ubuntuHomeI tried using ssh secure shell and putty in vista.... (11 Replies)
Discussion started by: Bandit390
11 Replies

5. SCO

/dev/inet/tcp not listening in SCO 6.

While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out? An early response will be appreciated. Thank you Regards TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies

6. Programming

Concurrent TCP client/server

I made a program and now I need to make it concurrent. Can someone pls help me do this ? The code is this: #include <sys/types.h> #include <sys/socket.h> #include <sys/time.h> #include <netinet/in.h> #include <errno.h> #include <unistd.h> #include <stdio.h> #include <string.h>... (4 Replies)
Discussion started by: Johnny22
4 Replies

7. Programming

[C++] [Unix] TCP non-blocking. Detect server disconnection procedure over, from client.

Hello! I searched forum for similar topic, with no luck, if you know one, delete this topic, and send me private message with link please. Little background: I have a lot of clients and one serwer. Client can make multiple connections on different ports and ips, but only one can be acctive... (2 Replies)
Discussion started by: ikeban
2 Replies

8. Red Hat

Memory problems in NFS client server

Hi all, i have some doubts in a situation that i fail to get an answer in Google. I have a solaris 10 nfs server and 5 centos 6.0 nfs clients. The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies

9. Solaris

Too much TCP retransmitted and TCP duplicate on server Oracle Solaris 10

I have problem with oracle solaris 10 running on oracle sparc T4-2 server. Os information: 5.10 Generic_150400-03 sun4v sparc sun4v Output from tcpstat.d script TCP bytes: out outRetrans in inDup inUnorder 6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies

10. Solaris

LDAP Client not connecting to LDAP server

I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful. The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
Mojo::IOLoop(3pm)					User Contributed Perl Documentation					 Mojo::IOLoop(3pm)

NAME
Mojo::IOLoop - Minimalistic reactor for non-blocking TCP clients and servers SYNOPSIS
use Mojo::IOLoop; # Listen on port 3000 Mojo::IOLoop->server({port => 3000} => sub { my ($loop, $stream) = @_; $stream->on(read => sub { my ($stream, $chunk) = @_; # Process input say $chunk; # Got some data, time to write $stream->write('HTTP/1.1 200 OK'); }); }); # Connect to port 3000 my $id = Mojo::IOLoop->client({port => 3000} => sub { my ($loop, $err, $stream) = @_; $stream->on(read => sub { my ($stream, $chunk) = @_; # Process input say "Input: $chunk"; }); # Write request $stream->write("GET / HTTP/1.1 "); }); # Add a timer Mojo::IOLoop->timer(5 => sub { my $loop = shift; $loop->remove($id); }); # Start loop if necessary Mojo::IOLoop->start unless Mojo::IOLoop->is_running; DESCRIPTION
Mojo::IOLoop is a very minimalistic reactor based on Mojo::Reactor, it has been reduced to the absolute minimal feature set required to build solid and scalable non-blocking TCP clients and servers. Optional modules EV, IO::Socket::INET6 and IO::Socket::SSL are supported transparently and used if installed. Individual features can also be disabled with the "MOJO_NO_IPV6" and "MOJO_NO_TLS" environment variables. A TLS certificate and key are also built right in to make writing test servers as easy as possible. Also note that for convenience the "PIPE" signal will be set to "IGNORE" when Mojo::IOLoop is loaded. See Mojolicious::Guides::Cookbook for more. ATTRIBUTES
Mojo::IOLoop implements the following attributes. "client_class" my $class = $loop->client_class; $loop = $loop->client_class('Mojo::IOLoop::Client'); Class to be used for opening TCP connections with the "client" method, defaults to Mojo::IOLoop::Client. "lock" my $cb = $loop->lock; $loop = $loop->lock(sub {...}); A callback for acquiring the accept mutex, used to sync multiple server processes. The callback should return true or false. Note that exceptions in this callback are not captured. $loop->lock(sub { my ($loop, $blocking) = @_; # Got the accept mutex, start listening return 1; }); "max_accepts" my $max = $loop->max_accepts; $loop = $loop->max_accepts(1000); The maximum number of connections this loop is allowed to accept before shutting down gracefully without interrupting existing connections, defaults to 0. Setting the value to 0 will allow this loop to accept new connections indefinitely. "max_connections" my $max = $loop->max_connections; $loop = $loop->max_connections(1000); The maximum number of parallel connections this loop is allowed to handle before stopping to accept new incoming connections, defaults to 1000. Setting the value to 0 will make this loop stop accepting new connections and allow it to shut down gracefully without interrupting existing connections. "reactor" my $reactor = $loop->reactor; $loop = $loop->reactor(Mojo::Reactor->new); Low level event reactor, usually a Mojo::Reactor::Poll or Mojo::Reactor::EV object. # Watch handle for I/O events $loop->reactor->io($handle => sub { my ($reactor, $writable) = @_; say $writable ? 'Handle is writable' : 'Handle is readable'; }); "server_class" my $class = $loop->server_class; $loop = $loop->server_class('Mojo::IOLoop::Server'); Class to be used for accepting TCP connections with the "server" method, defaults to Mojo::IOLoop::Server. "stream_class" my $class = $loop->stream_class; $loop = $loop->stream_class('Mojo::IOLoop::Stream'); Class to be used by "client" and "server" methods for I/O streams, defaults to Mojo::IOLoop::Stream. "unlock" my $cb = $loop->unlock; $loop = $loop->unlock(sub {...}); A callback for releasing the accept mutex, used to sync multiple server processes. Note that exceptions in this callback are not captured. METHODS
Mojo::IOLoop inherits all methods from Mojo::Base and implements the following new ones. "client" my $id = Mojo::IOLoop->client(address => '127.0.0.1', port => 3000, sub {...}); my $id = $loop->client(address => '127.0.0.1', port => 3000, sub {...}); my $id = $loop->client({address => '127.0.0.1', port => 3000}, sub {...}); Open TCP connection with "client_class", which is usually Mojo::IOLoop::Client, takes the same arguments as "connect" in Mojo::IOLoop::Client. # Connect to localhost on port 3000 Mojo::IOLoop->client({port => 3000} => sub { my ($loop, $err, $stream) = @_; ... }); "delay" my $delay = Mojo::IOLoop->delay; my $delay = $loop->delay; my $delay = $loop->delay(sub {...}); Get Mojo::IOLoop::Delay object to synchronize events and subscribe to event "finish" in Mojo::IOLoop::Delay if optional callback is provided. # Synchronize multiple events my $delay = Mojo::IOLoop->delay(sub { say 'BOOM!' }); for my $i (1 .. 10) { $delay->begin; Mojo::IOLoop->timer($i => sub { say 10 - $i; $delay->end; }); } # Wait for events if necessary $delay->wait unless Mojo::IOLoop->is_running; "generate_port" my $port = Mojo::IOLoop->generate_port; my $port = $loop->generate_port; Find a free TCP port, this is a utility function primarily used for tests. "is_running" my $success = Mojo::IOLoop->is_running; my $success = $loop->is_running; Check if loop is running. exit unless Mojo::IOLoop->is_running; "one_tick" Mojo::IOLoop->one_tick; $loop->one_tick; Run reactor until an event occurs or no events are being watched anymore. Note that this method can recurse back into the reactor, so you need to be careful. "recurring" my $id = Mojo::IOLoop->recurring(0 => sub {...}); my $id = $loop->recurring(3 => sub {...}); Create a new recurring timer, invoking the callback repeatedly after a given amount of time in seconds. # Invoke as soon as possible Mojo::IOLoop->recurring(0 => sub { say 'Reactor tick.' }); "remove" Mojo::IOLoop->remove($id); $loop->remove($id); Remove anything with an id, connections will be dropped gracefully by allowing them to finish writing all data in their write buffers. "server" my $id = Mojo::IOLoop->server(port => 3000, sub {...}); my $id = $loop->server(port => 3000, sub {...}); my $id = $loop->server({port => 3000}, sub {...}); Accept TCP connections with "server_class", which is usually Mojo::IOLoop::Server, takes the same arguments as "listen" in Mojo::IOLoop::Server. # Listen on port 3000 Mojo::IOLoop->server({port => 3000} => sub { my ($loop, $stream, $id) = @_; ... }); "singleton" my $loop = Mojo::IOLoop->singleton; The global Mojo::IOLoop singleton, used to access a single shared loop object from everywhere inside the process. # Many methods also allow you to take shortcuts Mojo::IOLoop->timer(2 => sub { Mojo::IOLoop->stop }); Mojo::IOLoop->start; "start" Mojo::IOLoop->start; $loop->start; Start the loop, this will block until "stop" is called or no events are being watched anymore. # Start loop only if it is not running already Mojo::IOLoop->start unless Mojo::IOLoop->is_running; "stop" Mojo::IOLoop->stop; $loop->stop; Stop the loop, this will not interrupt any existing connections and the loop can be restarted by running "start" again. "stream" my $stream = Mojo::IOLoop->stream($id); my $stream = $loop->stream($id); my $id = $loop->stream($stream); Get Mojo::IOLoop::Stream object for id or turn object into a connection. # Increase inactivity timeout for connection to 300 seconds Mojo::IOLoop->stream($id)->timeout(300); "timer" my $id = Mojo::IOLoop->timer(5 => sub {...}); my $id = $loop->timer(5 => sub {...}); my $id = $loop->timer(0.25 => sub {...}); Create a new timer, invoking the callback after a given amount of time in seconds. # Invoke as soon as possible Mojo::IOLoop->timer(0 => sub { say 'Next tick.' }); DEBUGGING
You can set the "MOJO_IOLOOP_DEBUG" environment variable to get some advanced diagnostics information printed to "STDERR". MOJO_IOLOOP_DEBUG=1 SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>. perl v5.14.2 2012-09-05 Mojo::IOLoop(3pm)
All times are GMT -4. The time now is 03:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy