Fedora Linux for Socket Program Development


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Fedora Linux for Socket Program Development
# 1  
Old 01-16-2008
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 which tells on setting an fedora core for development activities. I need all the ports to be open and no port blocking should be enabled on the fedora.

Please let me know.

Venky
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

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

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

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

4. Programming

Problem with Socket program..

I wrote a program which will send a message to multiple clients(i.e, broadcasting) that are connected to a server.Once when the client receives a message from the server ,the client should read a file in the server and display it in the client.The client which responds (i.e, client wants all the... (3 Replies)
Discussion started by: vigneshinbox
3 Replies

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

6. Linux

Socket Error for LAMP on Fedora 7

Hi. um. I'm trying to make a LAMP server on Fedora 7, but When I try to turn Apache/Httpd on, it gives me this error: # chkconfig -- levels 235 httpd on # /etc/init.d/httpd start Starting httpd: (98)Address already in use: make_sock: could not bind to address 192.168.1.110.80 no listening... (8 Replies)
Discussion started by: umja345
8 Replies

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

8. 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
Login or Register to Ask a Question
rpc_name_to_sockaddr(3ncs)												rpc_name_to_sockaddr(3ncs)

Name
       rpc_name_to_sockaddr - convert a host name and port number to a socket address (client or server)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$name_to_sockaddr(name, nlength, port, family, sockaddr,				slength, status)
       unsigned char name;
       unsigned long nlength;
       unsigned long port;
       unsigned long family;
       socket_$addr_t *sockaddr;
       unsigned long *slength;
       status_$t *status;

Arguments
       name		   A  string  that  contains  a host name and, optionally, a port and an address family.  The format is family:host[port],
			   where family: and [port] are optional.  If you specify a family as  part  of  the  name  parameter,	you  must  specify
			   socket_$unspec in the family parameter.  The family part of the name parameter is ip; host is the host name; port is an
			   integer port number.

       nlength		   The number of characters in name.

       port		   The socket port number.  This parameter should have the value rpc_$unbound_port if you are not specifying a	well-known
			   port;  in  this case, the returned socket address will specify the Local Location Broker (LLB) forwarding port at host.
			   If you specify the port number in the name parameter, this parameter is ignored.

       family		   The address family to use for the socket address.  This value corresponds to the communications protocol used to access
			   the socket and determines how the sockaddr is expressed.  If you specify the address family in the name parameter, this
			   parameter must have the value socket_$unspec.

       sockaddr 	   The socket address corresponding to name, port, and family.

       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 provides the socket address for a socket, given the host name, the port number, and the address family.

       You  can specify the socket address information either as one text string in the name parameter or by passing each of the three elements as
       separate parameters( name, port, and family ); in the latter case, the name parameter should contain only the hostname.

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.	This routine has been superseded by the routine.

Files
See Also
       intro(3ncs), rpc_sockaddr_to_name(3ncs), socket_from_name(3ncs)

															rpc_name_to_sockaddr(3ncs)