Re^2: A Simple Socket Server Using 'inetd'

http://qs1969.pair.com?node_id=634076

in reply to Re: A Simple Socket Server Using 'inetd'
in thread A Simple Socket Server Using 'inetd'

You can't, directly, of course. With netstat and arp you could figure it out, although the connection is transient.

Don Wilde
"There's more than one level to any answer."

Comment on Re^2: A Simple Socket Server Using 'inetd'

Replies are listed 'Best First'.
Re^3: A Simple Socket Server Using 'inetd' by fredo2906 (Acolyte) on Dec 30, 2007 at 03:30 UTC
Hey guys, Is it possible to get a sample of your SECSII client? I'd like to make a SECSII communication over TCP but seems to be difficult to me... Thanks a lot!	[reply]
Re^4: A Simple Socket Server Using 'inetd' by samizdat (Vicar) on Dec 31, 2007 at 15:47 UTC
I was working for Sandia Labs at the time, and under NDA. Sorry! It isn't that difficult, actually. It's just a simple binary protocol like any other, though there are some quirky things to it. :D Don Wilde "There's more than one level to any answer."	[reply]
Re^5: A Simple Socket Server Using 'inetd' by fredo2906 (Acolyte) on Jan 01, 2008 at 10:25 UTC
Thank you very much for your answer, even a 31 December... Actually I have a SECSII Client that can comunicate over TCP. So I would like to receive the characters sent by this client and log that into a file. If you have any idea or some sample to receive that and log it, that will help me much.	[reply]
Re^6: A Simple Socket Server Using 'inetd' by samizdat (Vicar) on Jan 02, 2008 at 13:41 UTC
Re^3: A Simple Socket Server Using 'inetd' by dellair (Initiate) on Jun 16, 2013 at 14:33 UTC
I am trying it out on Windows, set up inetd via Cygwin and start it as Windows service. It always prompt "Bad file descriptor". at: my $line = <STDIN> When I connect via "telnet localhost <port>". Would you please shed some lights on it? Thanks,	[reply]

In Section Tutorials