Sponsored Content
Top Forums Programming How to test a socket conncection in C++ ? Post 302380335 by vij_krr on Monday 14th of December 2009 11:22:03 PM
Old 12-15-2009
just forgot that line.. that is the configuration class. That method will return the socekt descriptor.
 

9 More Discussions You Might Find Interesting

1. Programming

Wireless C program conncection interruption problem

Dear Gurus My company has a wireless handheld C program as text-mode workstations in remote sites. We suspected that the program get interrupted sometimes because of out-of-wireless access and hence resulted in db record locking and other issue. It did trouble us a lot. Is it possible to use... (2 Replies)
Discussion started by: charles_chu
2 Replies

2. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, 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
0 Replies

3. Programming

which socket should socket option on be set

Hi all, On the server side, one socket is used for listening, the others are used for communicating with the client. My question is: if i want to set option for socket, which socket should be set on? If either can be set, what's the different? Again, what's the different if set option... (1 Reply)
Discussion started by: blademan100
1 Replies

4. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

5. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

6. Programming

socket function to read a webpage (socket.h)

Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct... #include <stdio.h> #include <stdlib.h> #include <sys/types.h> #include <sys/stat.h> #include <string.h> #include... (3 Replies)
Discussion started by: cyler
3 Replies

7. Programming

Error with socket operation on non-socket

Dear Experts, i am compiling my code in suse 4.1 which is compiling fine, but at runtime it is showing me for socket programming error no 88 as i searched in errno.h it is telling me socket operation on non socket, what is the meaning of this , how to deal with this error , please... (1 Reply)
Discussion started by: vin_pll
1 Replies

8. IP Networking

Clarification - Setting socket options at the same time when socket is listening

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
2 Replies

9. Programming

Using socket to test a TCP port

Hello, I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies
Net::Server::Log::Log::Log4perl(3)			User Contributed Perl Documentation			Net::Server::Log::Log::Log4perl(3)

NAME
Net::Server::Log::Log::Log4perl - log via Log4perl SYNOPSIS
use base qw(Net::Server::PreFork); __PACKAGE__->run( log_file => 'Log::Log4perl', log4perl_conf => '/path/to/my/log4perl.conf', log4perl_logger => 'myapp', ); DESCRIPTION
This module provides Log::Log4perl style logging to the Net::Server system. CONFIGURATION
log_file To begin using Log::Log4perl logging, simply set the Net::Server log_file configuration parameter to "Log::Log4perl". If the magic name "Log::Log4perl" is used, all logging will be directed to the Log4perl system. If used, the "log4perl_conf", "log4perl_poll", "log4perl_logger" may also be defined. log4perl_conf Only available if "log_file" is equal to "Log::Log4perl". This is the filename of the log4perl configuration file - see Log::Log4perl. If this is not set, will die on startup. If the file is not readable, will die. log4perl_poll If set to a value, will initialise with Log::Log4perl::init_and_watch with this polling value. This can also be the string "HUP" to re- read the log4perl_conf when a HUP signal is received. If set to 0, no polling is done. See Log::Log4perl for more details. log4perl_logger This is the facility name. Defaults to "Net::Server". DEFAULT ARGUMENTS FOR Net::Server The following arguments are available in the default "Net::Server" or "Net::Server::Single" modules. (Other personalities may use additional parameters and may optionally not use parameters from the base class.) Key Value Default ## log4perl parameters (if log_file eq Log::Log4perl) log4perl_conf "filename" will die if not set log4perl_poll number or HUP 0 (no polling) log4perl_logger "name" "Net::Server" METHODS
"initialize" This method is called during the initilize_logging method of Net::Server. It returns a single code ref that will be stored under the log_function property of the Net::Server object. That code ref takes log_level and message as arguments and calls the initialized log4perl system. LICENCE
Distributed under the same terms as Net::Server POD ERRORS
Hey! The above document had some coding errors, which are explained below: Around line 84: You forgot a '=back' before '=head1' Around line 93: '=item' outside of any '=over' Around line 129: Unknown directive: =over4 Around line 131: '=item' outside of any '=over' perl v5.16.2 2012-06-05 Net::Server::Log::Log::Log4perl(3)
All times are GMT -4. The time now is 03:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy