12-11-2005
Please make sure that you have read our
rules. And note:
(6) Do not post classroom or homework problems.
Once in a while we bend the rules a bit, so I'll make one suggestion before closing the thread. Your server children processes need to have a Unix domain socket to talk with the master server. (Use AF-UNIX instead of AF-INET.) Then read the man pages for the system calls sendmsg() and recvmsg(). Where they talk about sending "access rights" is what you want. Bear in mind that you will be creating a new fd that references the same open file as the old fd. So the sending process may send, say, fd 9 and the receiving process might establish, say, fd 21. This works for and fd, including any socket. And there is no other standard way to transfer an fd between processes.
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
talkd(8) System Manager's Manual talkd(8)
NAME
talkd, ntalkd - The remote communications server for the talk command
SYNOPSIS
talkd
ntalkd
DESCRIPTION
The talkd server notifies a user or callee when a client or caller wants to initiate a conversation. The talkd daemon sets up the conver-
sation if the callee accepts the invitation. The caller initiates a conversation by executing the talk command and specifying the callee.
The callee accepts the invitation by executing the talk command specifying the caller.
The talkd daemon listens at a socket for a LOOK_UP request from a local or remote talk client. On receiving a LOOK_UP request, talkd scans
its internal invitation table for an entry that pairs the client (the local or remote talk process) with a caller.
If an entry exists in the talkd daemon's international invitation table, the talkd daemon assumes that the client process is the callee.
The talkd daemon returns the appropriate rendezvous address to the talk process for the callee. The callee process then establishes a
stream connection with the caller process.
If an entry does not exist in the invitation table, the talkd daemon assumes that the client process is the caller. The talkd daemon then
receives the client process's ANNOUNCE request. When talkd receives the ANNOUNCE request, talkd broadcasts an invitation on the console of
the remote host where the callee is logged in, unless the caller specifies a particular tty. At approximately 1-minute intervals, talkd
rebroadcasts the invitation until either the invitation is answered by the callee or the call is canceled by the caller.
Debugging messages are sent to syslogd(8). For further information on the files used by this daemon, see the syslogd command.
FILES
Specifies the command path Defines Internet socket assignments Contains data about users who are currently logged in
NOTES
The Tru64 UNIX version of talkd uses the talk 4.3BSD protocol. This command is sometimes referred to as ntalkd. It is not compatible with
4.2BSD versions of talk.
RELATED INFORMATION
Commands: inetd(8), syslogd(8), talk(1) delim off
talkd(8)