🚀 go-pugleaf

In article <1990Nov6.015433.10642@mathrt0.math.chalmers.se> augustss@cs.chalmers.se (Lennart Augustsson) writes:
>In a language implementation that I am doing I've got the following
>problem: I'm using multiple processes (processors) to run a program,
>during the execution of the program it may be necessary to open files
>(and sockets).  After a file has been opened it would be desirable
>if all processes (and not just the one doing the open) could read from
>that file (the reason for this is to keep all processes "equal").
>I can see no clean solution to this problem.  The descriptor that the
>opening process gets back needs to be distributed to the others
>somehow, but as far as I know there is now mechanism for that.  Or is
>there?
>4.3 BSD Unix contains a way to distribute file descriptors through the
>sendmsg and recvmsg system calls, but as usual Sequent are years
>behind when it comes to the operating system (sendmsg&recvmsg can send



  There is no mention here of the Dynix rev currently on your machine. Under
Dynix 3.0.17,  the sendmsg() and recvmsg() calls are available.  It could
be as simple as an upgrade of the OS for you to be fble to draw on this
functionality.




>file descriptors in the UNIX domain on vanilla 4.3 BSD, Ultrix, and
>SunOS).
>Has anyone else had this problem?  Have you got any solutions?
>Hello Sequent, are you listening?  Are you ever going to catch up with

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  We are indeed listening!  Perhaps this issue could have been address
by Sequent Customer Service at the 800 number provided you by your sales
representative.  

  Please e-mail me if I can be of further assistance!




--
Kevin Closson
Sequent Technical Support
Database/Layered Products              x83072