From: Francisco J Ballesteros <nemo@lsub.org>
To: 9fans@9fans.net
Subject: Re: [9fans] two questions about go in Plan 9
Date: Mon, 18 Feb 2013 16:21:49 +0100 [thread overview]
Message-ID: <8DAE8251-7C0C-4940-849B-C18AFDCCEE54@lsub.org> (raw)
Forgive me,
Somehow I removed the -v from the call to go test. That makes the log print only for failed tests.
Regarding TCP, forsyth reminded me that it's what I'd get with the std. Plan 9 system calls, which
is so.
I guess my question is… how can I interrupt a reader in that case? In C I'd be able to interrupt it.
Now, in go on Plan 9, I can't interrupt it and I can't make the stream hangup.
What do you do in that case? Or, more likely, what am I doing wrong?
thanks
On Feb 18, 2013, at 4:07 PM, nemo@lsub.org wrote:
> Hi,
>
> I've been using go for a few things in Plan 9, and noticed a couple of things.
> I'd just like to know if it's me or if this also happens to others:
>
> - diagnostics issued by log.Print et al. don't show up unless I call log.Fail
> - closing a tcp connection which is still open by a nearby reader proc does not report EOF to the other end
> of the connection.
>
> It might be something I made or something I didn't understand, but just in case
> these are known I thought I might ask here.
>
> thanks
>
>
> [/mail/box/nemo/msgs/201302/876]
next reply other threads:[~2013-02-18 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 15:21 Francisco J Ballesteros [this message]
2013-02-18 16:51 ` lucio
-- strict thread matches above, loose matches on Subject: below --
2013-02-18 19:04 Nemo
2013-02-18 21:39 ` Skip Tavakkolian
2013-02-18 18:12 Francisco J Ballesteros
2013-02-18 18:22 ` Matthew Veety
2013-02-18 18:56 ` Akshat Kumar
2013-02-18 17:43 Nemo
2013-02-18 18:05 ` cinap_lenrek
2013-02-18 15:04 Francisco J Ballesteros
2013-02-18 15:16 ` Matthew Veety
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=8DAE8251-7C0C-4940-849B-C18AFDCCEE54@lsub.org \
--to=nemo@lsub.org \
--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).