12-11-2005
Sockets and File descriptors
I am in a Systems programming class this semester, and our current project is to write a program utilizing sockets and fork. For the project, I decided to make my own instant messaging program. I have the code completed, but I have a problem that keeps old clients from communicating with new clients. The way it is currently set up has 2 programs, a client and a server. The server is always running. Each time a client connects, it forks off a child process to handle communication with that client, then the parent goes back to listening for new clients. On the client side, a connection to the server is made and communication is done with its associated server child process. Each time the server forks, it passes the updated table of file descriptors to its new child. However, child processes that already exist don't have record of the new file descriptor, which keeps them from being able to communicate to other users.
Take this example. Client A signs on. Then Client B. Client B can send messages to Client A, but Client A cannot send messages to client B because Client B signed on after client A, so he doesn't have the file descriptor for B. Client C then signs on. He can communicate with A and B because he has a current list of file descriptors for the users. But B cannot communicate with C and A can't communicate with either. I obviously would like all clients to communicate with one another no matter when they signed on.
Essentially, I would like a way to update file descriptors on all of the children each time a new client signs on. But that may not be the best solution to the problem. All I really need is a way for clients to communicate no matter when they signed on and without creating a seperate socket between each client. Any ideas?
Thanks for your help.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I have written a daemon process, to perform certain operations in the background.
For this I have to close, the open file descriptors,
Does anybody know how to find out the number of open file descriptors ?
Thanks in Advance,
Sheetal (2 Replies)
Discussion started by: s_chordia
2 Replies
2. UNIX for Advanced & Expert Users
Hello all,
A few questions on file descriptors ...
scenario : Sun Ultra 30 with Sun OS 5.5.1 , E250 with Solaris 2.6
In one of my servers, the file descriptor status from the soft limit and hard limits are 64 and 1024 respectively for root user.
Is the soft limit (64) represents the... (3 Replies)
Discussion started by: shibz
3 Replies
3. UNIX for Dummies Questions & Answers
i m trying to learn processes in unix and i've been reading this but i don't quite get it. its regarding file descriptors. : each is a part of file pointers, they point to another area. indexes into an Operating system maintained table called "file descriptor table". one table per process. may... (3 Replies)
Discussion started by: a25khan
3 Replies
4. Shell Programming and Scripting
Greetings,
I have a troubling problem with a Korn Shell concept that I know works in Solaris.
Essentially I am assigning file descriptors to a coprocess. Also, it should be noted that I am not using the public domain ksh but, rather AT&T ksh93.
Here is a test scenario:
$ sqlplus -s... (5 Replies)
Discussion started by: tmarikle
5 Replies
5. Shell Programming and Scripting
I have a script that creates a KSH co-process for Oracle sqlplus and I am presently interacting with it via print -p and read -p.
I also need to interact with another Oracle database what isn't permitted to have any direct connection to the first. Presently, I simply disconnect from the first... (10 Replies)
Discussion started by: tmarikle
10 Replies
6. UNIX for Advanced & Expert Users
Hi All,
This thread is going to be a discussion basically bringing out more information from the experts on cron jobs and the associated file handles.
So, here is the question.
There is definitely a constant ' n ' as the maximum number of file handles alloted to a process ' p '.
Will... (7 Replies)
Discussion started by: matrixmadhan
7 Replies
7. UNIX for Dummies Questions & Answers
I have written this code, and according to my research it SHOULD be going down the list until it is finished, but I am getting blank feedback. Nothing is being output as far as I can tell.
#!/bin/sh
while echo Enter to start traversing
read enter
do
read list <&3
echo $list
done
any... (2 Replies)
Discussion started by: MaestroRage
2 Replies
8. HP-UX
Hi,
I speak and write english more or less, so I hope my asking be clear.
:)
In the company I am working, they are using control-m software to lunch
shell scripts.
So i put this command in all shell scripts:
export LOGFILE_tmp=$PRODUC_DATA/tmp/${SCRIPT}_${PAIS}_`date... (0 Replies)
Discussion started by: anamcara
0 Replies
9. UNIX for Dummies Questions & Answers
What is the difference between a file descriptor and a semaphore?
My basic understanding is:
- a file descriptor is a small positive integer that the system uses instead of the file name to identify an open file or socket.
- a semaphore is a variable with a value that indicates the... (1 Reply)
Discussion started by: Mr_Webster
1 Replies
10. Shell Programming and Scripting
Hi, I'm playing with KSH
I entered following command in terminal
{ echo "stdout" >&1; echo "stderr" >&2; } > out
And I get only stoud in a new file out.
My question is: Where did my stderr vanish ? (5 Replies)
Discussion started by: solaris_user
5 Replies
xpa(7) SAORD Documentation xpa(7)
NAME
XPA - Public Access to Data and Algorithms
SYNOPSIS
This document is the Table of Contents for XPA.
DESCRIPTION
The XPA messaging system provides seamless communication between many kinds of Unix programs, including X programs and Tcl/Tk programs. It
also provides an easy way for users to communicate with XPA-enabled programs by executing XPA client commands in the shell or by utilizing
such commands in scripts. Because XPA works both at the programming level and the shell level, it is a powerful tool for unifying any
analysis environment: users and programmers have great flexibility in choosing the best level or levels at which to access XPA services,
and client access can be extended or modified easily at any time.
A program becomes an XPA-enabled server by defining named points of public access through which data and commands can be exchanged with
other client programs (and users). Using standard TCP sockets as a transport mechanism, XPA supports both single-point and broadcast mes-
saging to and from these servers. It supports direct communication between clients and servers, or indirect communication via an interme-
diate message bus emulation program. Host-based access control is implemented, as is as the ability to communicate with XPA servers across
a network.
XPA implements a layered interface that is designed to be useful both to software developers and to users. The interface consists of a
library of XPA client and server routines for use in C/C++ programs and a suite of high-level user programs built on top of these
libraries. Using the XPA library, access points can be added to Tcl/Tk programs, Xt programs, or to Unix programs that use the XPA event
loop or any event loop based on select(). Client access subroutines can be added to any Tcl/Tk, Xt, or Unix program. Client access also is
supported at the command line via a suite of high-level programs.
Choose from the following topics:
o Introduction to XPA [xpaintro(7)]
o Access Point Names and Templates [xpatemplate(7)]
o Getting Common Information About Access Points [xpacommon(7)]
o Communication Methods [xpamethod(7)]
o Communication Between Hosts [xpainet(7)]
o Distinguishing Users [xpausers(7)]
o XPA User Programs
o xpaget: get data and info [xpaget(1)]
o xpaset: send data and info [xpaset(1)]
o xpainfo: send info alert [xpainfo(1)]
o xpaaccess: get access point info [xpaaccess(1)]
o xpamb: message bus emulation [xpamb(1)]
o xpans: the XPA name server [xpans(1)]
o XPA Server Routines
o XPANew: define a new access point [xpanew(3)]
o XPACmdNew: define a new command access point [xpacmdnew(3)]
o XPACmdAdd: add a command [xpacmdadd(3)]
o XPACmdDel: delete a command [xpacmddel(3)]
o XPAInfoNew: define an info access point [xpainfonew(3)]
o XPAFree: free an access point [xpafree(3)]
o XPAMainLoop: event loop for select server [xpamainloop(3)]
o XPAPoll: poll for XPA events [xpapoll(3)]
o XPACleanup: release reserved XPA memory [xpacleanup(3)]
o XPA Server Macros: accessing structure internals [xpamacros(3)]
o XPA Race Conditions: how to avoid them [xparace(3)]
o XPA Out of Memory (OOM) errors [xpaoom(3)]
o XPA Client Routines
o XPAOpen: open a persistent client connection [xpaopen(3)]
o XPAClose: close persistent client connection [xpaclose(3)]
o XPAGet: get data [xpaget(3)]
o XPASet: send data or commands [xpaset(3)]
o XPAInfo: send an info alert [xpainfo(3)]
o XPAGetFd: get data and write to an fd [xpagetfd(3)]
o XPASetFd: read data from and fd and send [xpasetfd(3)]
o XPANSLookup: look up an access point [xpanslookup(3)]
o XPAAccess: get access info [xpaaccess(3)]
o The XPA/Xt Interface: Xt interface to XPA [xpaxt(7)]
o The XPA/Tcl Interface: Tcl interface to XPA [xpa(3tcl)]
o Tailoring the XPA Environment
o Environment Variables [xpaenv(7)]
o Access Control [xpaacl(7)]
o Miscellaneous
o Where to Find Example/Test Code
o User Changes Between XPA 1.0 and 2.0
o API Changes Between XPA 1.0 and 2.0
o What Does XPA Stand For, Anyway?
version 2.1.14 June 7, 2012 xpa(7)