Hello,
I actually try to make client-server program.
I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error :
I'm just using this simple code :
and I get the same error if I use :
If someone can help me,
Thanks (2 Replies)
Hi ,
I'm facing the following problem in socket programming.
My structure is
struct {
int i;
char *str;
}samp;
I'm creating the pointer to this structure and assigning the value to the structure members and send via the socket to the another process.
The receiver process when... (7 Replies)
Hello Everyone
Iam working on tcp/ip programming.with some time interval server has to send data.client has to close the connection and to open the connection between the time interval.this is the scenario
when iam closing the connection in client side the connection terminates.how to... (1 Reply)
Hi,
I wanted to write a socket program in C, where I always want my socket connected to the server. i.e i shouldn't get disconnected once i get the response back from the server. I want to work in the connected mode, instead of disconnect and connect.
Can somebody please kindly provide me a... (3 Replies)
Hello experts,
four machines need to communicate with each other. How can I start the socket programming. Can you please explain me more elaborated way.
Thank you for your time and effort in advance (4 Replies)
hi guys i got this code trying to make connection between the server and multi clients but when i do ./server i got message server waiting then when i run ./client it says client 1 nosuch file i dont know whats that should i use any argument plz help how to compile and run and whats the expected... (1 Reply)
in socket programming how can i : Create for example 3 blank files, namely: server, client, network
•Server: act as servers/provider, will receive all requests from different client
•Client: requesters
•Network: middle-layer of communication between server & client
any tips or... (6 Replies)
i'm doing a simple program in socket programming on c i have server that can handle 2clients in a single machine i'm running ubuntu linux so i got it work but the probelm when clients send a message the server will echo it but i cant distinguish which client send the message client 1 or client... (7 Replies)
HI
Can anyone provide me with codes for file transfer server to client or vice versa?
Also please explain how to compile those programs in ubuntu terminal as i am totally new to socket programming.
Thanks (1 Reply)
Discussion started by: mayhemtrigger
1 Replies
LEARN ABOUT DEBIAN
ipsec_optionsfrom
IPSEC_OPTIONSFROM(3) 16 Oct 1998 IPSEC_OPTIONSFROM(3)NAME
ipsec_optionsfrom - read additional ``command-line'' options from file
SYNOPSIS
#include <freeswan.h>
const char *optionsfrom(char * filename, int * argcp, char *** argvp, int optind, FILE * errsto);
DESCRIPTION
Optionsfrom is called from within a getopt_long(3) scan, as the result of the appearance of an option (preferably --optionsfrom) to insert
additional "command-line" arguments into the scan immediately after the option. Typically this would be done to pick up options which are
security-sensitive and should not be visible to ps(1) and similar commands, and hence cannot be supplied as part of the actual command line
or the environment.
Optionsfrom reads the additional arguments from the specified filename, allocates a new argument vector to hold pointers to the existing
arguments plus the new ones, and amends argc and argv (via the pointers argcp and argvp, which must point to the argc and argv being
supplied to getopt_long(3)) accordingly. Optind must be the index, in the original argument vector, of the next argument.
If errsto is NULL, optionsfrom returns NULL for success and a pointer to a string-literal error message for failure; see DIAGNOSTICS. If
errsto is non-NULL and an error occurs, optionsfrom prints a suitable complaint onto the errsto descriptor and invokes exit with an exit
status of 2; this is a convenience for cases where more sophisticated responses are not required.
The text of existing arguments is not disturbed by optionsfrom, so pointers to them and into them remain valid.
The file of additional arguments is an ASCII text file. Lines consisting solely of white space, and lines beginning with #, are comments
and are ignored. Otherwise, a line which does not begin with - is taken to be a single argument; if it both begins and ends with
double-quote ("), those quotes are stripped off (note, no other processing is done within the line!). A line beginning with - is considered
to contain multiple arguments separated by white space.
Because optionsfrom reads its entire file before the getopt_long(3) scan is resumed, an optionsfrom file can contain another --optionsfrom
option. Obviously, infinite loops are possible here. If errsto is non-NULL, optionsfrom considers it an error to be called more than 100
times. If errsto is NULL, loop detection is up to the caller (and the internal loop counter is zeroed out).
EXAMPLE
A reasonable way to invoke optionsfrom would be like so:
#include <getopt.h>
struct option opts[] = {
/* ... */
"optionsfrom", 1, NULL, '+',
/* ... */
};
int
main(argc, argv)
int argc;
char *argv[];
{
int opt;
extern char *optarg;
extern int optind;
while ((opt = getopt_long(argc, argv, "", opts, NULL)) != EOF)
switch (opt) {
/* ... */
case '+': /* optionsfrom */
optionsfrom(optarg, &argc, &argv, optind, stderr);
/* does not return on error */
break;
/* ... */
}
/* ... */
SEE ALSO getopt_long(3)DIAGNOSTICS
Errors in optionsfrom are: unable to open file; attempt to allocate temporary storage for argument or argument vector failed; read error in
file; line too long.
HISTORY
Written for the FreeS/WAN project by Henry Spencer.
BUGS
The double-quote convention is rather simplistic.
Line length is currently limited to 1023 bytes, and there is no continuation convention.
The restriction of error reports to literal strings (so that callers don't need to worry about freeing them or copying them) does limit the
precision of error reporting.
The error-reporting convention lends itself to slightly obscure code, because many readers will not think of NULL as signifying success.
There is a certain element of unwarranted chumminess with the insides of getopt_long(3) here. No non-public interfaces are actually used,
but optionsfrom does rely on getopt_long(3) being well-behaved in certain ways that are not actually promised by the specs.
16 Oct 1998 11/14/2008 IPSEC_OPTIONSFROM(3)