From: "Pavel Klinkovský" <pavel.klinkovsky@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Failed 'reject' function?
Date: Fri, 10 Oct 2014 11:28:50 +0200 [thread overview]
Message-ID: <CAGNd-2NQUQWiGjPaNC5ohBU6nKtnxq6pr+VNMVLv5VRhrfh2dg@mail.gmail.com> (raw)
In-Reply-To: <CAOFTvP+SO-GOAo_uyJUVAOJrX2akp3AnAdkiJFzw-KpSoo+HSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
Hi Sergey,
It seems, you do it incorrectly :) dial(2) has an exact example if using
> announce/listen/accept functions.
>
I do exactly what I need. ;)
The sequence announce/listen/accept is very well known to me.
But I need both possibilities:
- accept incoming connection
- reject incoming connection, which failed.
Thank to Charles, I finally understood.
Pavel
[-- Attachment #2: Type: text/html, Size: 759 bytes --]
next prev parent reply other threads:[~2014-10-10 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 7:48 Pavel Klinkovský
2014-10-10 9:22 ` Charles Forsyth
2014-10-10 9:23 ` Charles Forsyth
2014-10-10 9:24 ` Sergey Zhilkin
2014-10-10 9:28 ` Pavel Klinkovský [this message]
2014-10-10 9:32 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGNd-2NQUQWiGjPaNC5ohBU6nKtnxq6pr+VNMVLv5VRhrfh2dg@mail.gmail.com \
--to=pavel.klinkovsky@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).