10 More Discussions You Might Find Interesting
1. AIX
Hello,
Is there any API or any other approach to detect whether the network cable is connected to the network adapter, say, en0, en1 or en2?
The OS is AIX6.1.
Thank you. (4 Replies)
Discussion started by: zephyrbj
4 Replies
2. Programming
Hi,
I want to code TCP/IP client/server in linux application capable to fastly detect ethernet cable disconnection in any condition.
So I have activate SO_KEEPALIVE options and set TCP_KEEPCNT, TCP_KEEPIDLE and TCP_KEEPINTVL to 1.
When I disconnect ethernet cable I have the following... (5 Replies)
Discussion started by: jeje_clb
5 Replies
3. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
4. Programming
Hi everyone,
I'm new to this forum. I'm working on new project for last few days and this forum already helped me on
couple of occasions. I don't have any prior experience with network programming so I'll appreciate any advise given.
I'm trying to do the following:
1. open user... (2 Replies)
Discussion started by: _thomas
2 Replies
5. IP Networking
Hi,
I'm trying to communicate two servers (HP DLProliant 380 G5) via a crossover cable, but I don't get them to ping each other.
I am working in RHEL 4.
These are the steps I've performed:
1) Plugged the crossover cables in eth2.
(note: The cable is brand new. Also I built one myself... (3 Replies)
Discussion started by: jrodriguez365
3 Replies
6. Programming
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)
Discussion started by: kedah160
1 Replies
7. Red Hat
hi..
I unplug my eth0 lan cable.. and suddenly my system shutdown... no idea :eek::confused: (3 Replies)
Discussion started by: flekzout
3 Replies
8. Programming
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)
Discussion started by: arunviswanath
7 Replies
9. Programming
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)
Discussion started by: soshell
2 Replies
10. Programming
Dear Reader,
Is there any way to check up socket status other than 'netstatus '
Thanks in advance, (1 Reply)
Discussion started by: joseph_shibu
1 Replies
rpc_use_family_wk(3ncs) rpc_use_family_wk(3ncs)
Name
rpc_use_family_wk - create a socket with a well-known port for a remote procedure call (RPC) server (server only)
Syntax
#include <idl/c/rpc.h>
void rpc_$use_family_wk(family, ifspec, sockaddr, slength, status)
unsigned long family;
rpc_$if_spec_t *ifspec;
socket_$addr_t *sockaddr;
unsigned long *slength;
status_$t *status;
Arguments
family The address family of the socket to be created. This value corresponds to the communications protocol used to access the
socket and determines how the sockaddr is expressed. The value must be one of socket_$unspec or socket_$internet.
ifspec The interface that will be registered by the server. Typically, this parameter is the interface if_spec generated by the
NIDL compiler from the interface definition; the well-known port is specified as an interface attribute.
sockaddr The socket address of the socket on which the server will listen.
slength The length, in bytes, of sockaddr.
status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it was
successful.
Description
The routine creates a socket that uses the port specified through the if_spec parameter. Use this routine to create a socket only if a
server must listen on a particular well-known port. Otherwise, use
A server listens on one socket per address family, regardless of how many interfaces that it exports. Therefore, servers that use well-
known ports should make this call once per supported address family.
Examples
The following statement creates the well-known socket identified by for an array processor server:
rpc_$use_family_wk (socket_$internet, &matrix$if_spec,
&sockaddr, &slen, &status);
Diagnostics
This section lists status codes for errors returned by this routine in
rpc_$cant_create_sock
The RPC runtime library was unable to create a socket.
rpc_$not_in_call An internal error.
rpc_$proto_error An internal protocol error.
rpc_$too_many_sockets
The server is trying to use more than the maximum number of sockets that is allowed; it has called or too many times.
rpc_$bad_pkt The server or client has received an ill-formed packet.
rpc_$addr_in_use The address and port specified in an routine are already in use. This is caused by multiple calls to with the same
well-known port.
Files
See Also
intro(3ncs), rpc_use_family(3ncs)
rpc_use_family_wk(3ncs)