| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | sockets with emx/gcc & w |
Hallo, Jonathan!
*** Am Sonntag 28. Juli 1996 um 22:16 schrieb Jonathan de Boyne Pollard an
Brett Maxfield:
JdBP> Write a daemon that can be invoked from inetd, update the information
JdBP> in the inetd configuration file, and let inetd do all of the hard work
JdBP> of accepting the connections for you.
writing daemons for inetd is a dirty piece of work with OS/2. This is
unlike the Unix approach. OS/2 inetd frees the port handle it sends to the
sub process, and you have to use undocumented calls to re-import the port
handle so that it is usable with further TCP/IP api calls. Mattes
elaborated on this topic some time ago on the emx mailing list
(emx{at}iaehv.nl). I will try to find the article and post it here.
Afair, the reason for this behaviour was that inetd doesn't track the
status of the child and frees the port handle in advance to not miss
freeing it when the child doesn't terminate correctly.
It is no big problem to accept() connections, then start a thread with the
new porthandle.
Tschau...Thomas
--- E3-32/1.11-32/2.50+
* Origin: Die TeX-Box +49-6034-930021 V.34 -930022 ISDN 24h (2:244/1130.42)SEEN-BY: 50/99 270/101 620/243 625/100 711/401 409 410 413 430 808 809 934 SEEN-BY: 711/955 712/407 515 624 628 713/888 800/1 @PATH: 244/1130 24/999 888 396/1 270/101 712/515 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.