Sponsored Content
Top Forums Programming Problem with Socket program.. Post 302307067 by Corona688 on Tuesday 14th of April 2009 01:55:30 PM
Old 04-14-2009
Quote:
Originally Posted by vigneshinbox
The client program should be able to retrieve data in a file in the server when the client sends a reply to the server. But it's not happening

Unless your computer actually has the IP address 10.142.17.123, then connecting to 10.142.17.123 isn't going to work. When your client and server programs are on the same machine, you can expect the address 127.0.0.1 to work.

Otherwise, please be more specific. Don't tell me what you ultimately want it to do("retrieve data in a file") but the procedure involved.
 

10 More Discussions You Might Find Interesting

1. Programming

How can I program socket in unix?

Excuse me . I'm a beginner . In windows , MFC can be used , but how to do in Unix ? And does unix support c++like VC++ ? How can I get developing tools in Unix ? (7 Replies)
Discussion started by: sanjohn
7 Replies

2. Programming

Socket Problem

Hi all, I have developed server/client application (using C) and tested it on the same machine .. but when I deploy them on different machines I get connection timeout. Well .. server machine and client machine exists on different network segments, so there is a linux firewall box to route... (3 Replies)
Discussion started by: Agent007
3 Replies

3. Programming

Help Socket program

Hi All, I'm writing a client-server socket program. the client will be an instance of the well-known telnet application. i want to implement a simple authentication between the server and the client. - the client should send this message (after the connection established): my password... (0 Replies)
Discussion started by: mhetfield
0 Replies

4. UNIX for Advanced & Expert Users

Fedora Linux for Socket Program Development

Hi, I am trying to port a networking application to linux, I get error while binding a socket to a port, The port is not used by any application and was verified by using netstat and other tools. I tried a simple socket and bind on a unused port, but even that fails. Is there any document... (0 Replies)
Discussion started by: venkatesh.n
0 Replies

5. UNIX for Advanced & Expert Users

problem with socket reading

I am not able to receive the message on socket in the current process when its waiting for its child to exit. code looks something like below //in one thread of the current process //thread 1 =============================================== int numBytes = read(sockid,buf,SIZE); //Now the... (2 Replies)
Discussion started by: swap007
2 Replies

6. 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

7. Shell Programming and Scripting

socket program

All, I am looked to develop a socket program from one Solaris server to another Solaris server to send UDP packets from a source UDP port number 2505 on the first server to the source port 2505 on the second server. Is it possible to do? What is the best way to do this? I want to set the... (1 Reply)
Discussion started by: bubba112557
1 Replies

8. UNIX for Dummies Questions & Answers

Help to run this socket program in C

i have created two files named server and client then when i run the server program it says the server is waiting(./server 5555) then when i run the client program it says "client error:connection refused" can u plz help me to run it?:( (7 Replies)
Discussion started by: kedah160
7 Replies

9. AIX

Sample C program to Send/Recieve a file using Socket

Hi All, I urgently need a Sample C program to Send/Recieve a file using Socket. Thanks Sara (1 Reply)
Discussion started by: saraperu
1 Replies

10. UNIX for Advanced & Expert Users

C socket program on UNIX

Write a C socket program on UNIX where a TCP client sends/reads a time in decimal 24 hours format to the server and the server echoes the seconds, minutes, and hours in the time. Example: Client sends 18.78 hours and the server displays 18 hours, 46 minutes and 48 seconds. (1 Reply)
Discussion started by: adi_always4u143
1 Replies
qmail-queue(8)						      System Manager's Manual						    qmail-queue(8)

NAME
qmail-queue - queue a mail message for delivery SYNOPSIS
qmail-queue DESCRIPTION
qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. It places the message into the outgoing queue for future delivery by qmail-send. The envelope information is an envelope sender address followed by a list of envelope recipient addresses. The sender address is preceded by the letter F and terminated by a 0 byte. Each recipient address is preceded by the letter T and terminated by a 0 byte. The list of recipient addresses is terminated by an extra 0 byte. If qmail-queue sees end-of-file before the extra 0 byte, it aborts without placing the message into the queue. Every envelope recipient address should contain a username, an @ sign, and a fully qualified domain name. qmail-queue always adds a Received line to the top of the message. Other than this, qmail-queue does not inspect the message and does not enforce any restrictions on its contents. However, the recipients probably expect to see a proper header, as described in qmail-header(5). Programs included with qmail which invoke qmail-queue will invoke the contents of $QMAILQUEUE instead, if that environment variable is set. FILESYSTEM RESTRICTIONS
qmail-queue imposes two constraints on the queue structure: each mess subdirectory must be in the same filesystem as the pid directory; and each todo subdirectory must be in the same filesystem as the intd directory. EXIT CODES
qmail-queue does not print diagnostics. It exits 0 if it has successfully queued the message. It exits between 1 and 99 if it has failed to queue the message. All qmail-queue error codes between 11 and 40 indicate permanent errors: 11 Address too long. 31 Mail server permanently refuses to send the message to any recipients. (Not used by qmail-queue, but can be used by programs offering the same interface.) All other qmail-queue error codes indicate temporary errors: 51 Out of memory. 52 Timeout. 53 Write error; e.g., disk full. 54 Unable to read the message or envelope. 55 Unable to read a configuration file. (Not used by qmail-queue.) 56 Problem making a network connection from this host. (Not used by qmail-queue.) 61 Problem with the qmail home directory. 62 Problem with the queue directory. 63 Problem with queue/pid. 64 Problem with queue/mess. 65 Problem with queue/intd. 66 Problem with queue/todo. 71 Mail server temporarily refuses to send the message to any recipients. (Not used by qmail-queue.) 72 Connection to mail server timed out. (Not used by qmail-queue.) 73 Connection to mail server rejected. (Not used by qmail-queue.) 74 Connection to mail server succeeded, but communication failed. (Not used by qmail-queue.) 81 Internal bug; e.g., segmentation fault. 91 Envelope format error. SEE ALSO
addresses(5), envelopes(5), qmail-header(5), qmail-inject(8), qmail-qmqpc(8), qmail-send(8), qmail-smtpd(8) qmail-queue(8)
All times are GMT -4. The time now is 08:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy