01-21-2010
The system logs might let you know if the program crashed etc. Its own logs might tell you if it halted suddenly or did a graceful shutdown for some reason. Other things to kill it could be the IP address changing, or the interface going down and up, but those aren't likely to happen to a server.
10 More Discussions You Might Find Interesting
1. Programming
i am programming a tcp_ip server which intends to listen permanently to a client . the client can disconnect and connect again and the server accept it(by this point it works).The problem is when the client lose connection without a disconnect command and my code can't get it and keeps waiting for... (4 Replies)
Discussion started by: massimo_ratti
4 Replies
2. IP Networking
Requirements:
A server program should read a file and send the message to the client . if the file is not there, then switch to the receive part of the same program and receive any messages from the socket. If no messages to receive then switch to send part of the program to... (2 Replies)
Discussion started by: Rajeshsu
2 Replies
3. UNIX for Dummies Questions & Answers
I have true64 Unix running and there a scales in the sytem which connect thru a com-server to the network. they have their own IP-address and are communicating over port 8000. when I telnet to the com-servers and the print function of the scale is executed I can see the data coming.
I need to know... (1 Reply)
Discussion started by: albinhess
1 Replies
4. Programming
Please tell me according to C/C++ socket programming; how client can check whether server is running or not during TCP communication. (1 Reply)
Discussion started by: mansoorulhaq
1 Replies
5. Programming
Hi,
I am new to using threads in C++ though I have been wkring on C++ for past 1.5 years...I want to write a TCP server that serves multiple client connections...to start off..i have been working on a simple tcp echo server trying to understand how threads work....
this is my server code:
... (5 Replies)
Discussion started by: deepti_v25
5 Replies
6. Programming
Hello @ all,
I hope you can give me some advice :b:
I will be following code for a tcp server and doStuff () function, the
clients treated. From some point, I have several identical
clients (zombies, I think), the same records in the database
write. Has anyone an explanation? What can I... (1 Reply)
Discussion started by: yumos
1 Replies
7. Programming
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
8. Solaris
Hi,
I am having a solaris server. I want to start a dummy TCP listner on UNIX OS on a specific port can anyone please let me know the process.
IP ADDRESS: 123.123.123.123
Port: 8010 (1 Reply)
Discussion started by: mayank2211
1 Replies
9. UNIX for Dummies Questions & Answers
I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies
10. Solaris
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
LEARN ABOUT SUSE
http::daemon::ssl
SSL(3) User Contributed Perl Documentation SSL(3)
NAME
HTTP::Daemon::SSL - a simple http server class with SSL support
SYNOPSIS
use HTTP::Daemon::SSL;
use HTTP::Status;
# Make sure you have a certs/ directory with "server-cert.pem"
# and "server-key.pem" in it before running this!
my $d = HTTP::Daemon::SSL->new || die;
print "Please contact me at: <URL:", $d->url, ">
";
while (my $c = $d->accept) {
while (my $r = $c->get_request) {
if ($r->method eq 'GET' and $r->url->path eq "/xyzzy") {
# remember, this is *not* recommened practice :-)
$c->send_file_response("/etc/passwd");
} else {
$c->send_error(RC_FORBIDDEN)
}
}
$c->close;
undef($c);
}
DESCRIPTION
Instances of the HTTP::Daemon::SSL class are HTTP/1.1 servers that listen on a socket for incoming requests. The HTTP::Daemon::SSL is a
sub-class of IO::Socket::SSL, so you can perform socket operations directly on it too.
The accept() method will return when a connection from a client is available. In a scalar context the returned value will be a reference
to a object of the HTTP::Daemon::ClientConn::SSL class which is another IO::Socket::SSL subclass. In a list context a two-element array is
returned containing the new HTTP::Daemon::ClientConn::SSL reference and the peer address; the list will be empty upon failure. (Note that
version
1.02 erroneously did not honour list context). Calling the get_request() method on the HTTP::Daemon::ClientConn::SSL object will read data
from the client and return an HTTP::Request object reference.
This HTTPS daemon does not fork(2) for you. Your application, i.e. the user of the HTTP::Daemon::SSL is reponsible for forking if that is
desirable. Also note that the user is responsible for generating responses that conform to the HTTP/1.1 protocol. The
HTTP::Daemon::ClientConn class provides some methods that make this easier.
METHODS
The following methods are the only differences from the HTTP::Daemon base class:
$d = new HTTP::Daemon::SSL
The constructor takes the same parameters as the IO::Socket::SSL constructor. It can also be called without specifying any parameters,
but you will have to make sure that you have an SSL certificate and key for the server in certs/server-cert.pem and
certs/server-key.pem. See the IO::Socket::SSL documentation for how to change these default locations and specify many other aspects
of SSL behavior. The daemon will then set up a listen queue of 5 connections and allocate some random port number. A server that wants
to bind to some specific address on the standard HTTPS port will be constructed like this:
$d = new HTTP::Daemon::SSL
LocalAddr => 'www.someplace.com',
LocalPort => 443;
SEE ALSO
RFC 2068
IO::Socket::SSL, HTTP::Daemon, Apache
COPYRIGHT
Code and documentation from HTTP::Daemon Copyright 1996-2001, Gisle Aas Changes Copyright 2003-2004, Peter Behroozi
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
POD ERRORS
Hey! The above document had some coding errors, which are explained below:
Around line 164:
You forgot a '=back' before '=head1'
perl v5.12.1 2008-02-12 SSL(3)