From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: mark.d.witmer@gmail.com
Cc: guile-user@gnu.org
Subject: Re: Trouble w/sockets
Date: Mon, 04 Mar 2013 11:02:58 +0100 [thread overview]
Message-ID: <87obezpjn1.fsf@zigzag.favinet> (raw)
In-Reply-To: <87zjyjkdbb.fsf@gmail.com> (mark d. witmer's message of "Sun, 03 Mar 2013 23:18:32 -0500")
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
() mark.d.witmer@gmail.com
() Sun, 03 Mar 2013 23:18:32 -0500
Using writev() gets rid of the broken pipe error and I successfully
write my connection initiation request to the X server.
If you can prove this, then perhaps you have found a bug in the server.
but I probably need to take a break from this for a while
Another idea is to restart X. I remember that helped sometimes. In
theory, failed connection attempts should not leave persistent changes
in the server state (modulo incremented counters), but it's also true
that the vast majority of client interactions are via Xlib (et al), so
there might be some shared quirks (both server and Xlib are wrong
somehow but that's OK because they are "compatibly wrong") in play.
Anyway, the point is: killing X is a good excuse to take a break. :-D
--
Thien-Thi Nguyen
GPG key: 4C807502
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-03-04 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 3:38 Trouble w/sockets mark
2013-03-03 4:48 ` Mike Gran
2013-03-03 5:36 ` mark
2013-03-03 6:35 ` Mike Gran
2013-03-03 7:29 ` Thien-Thi Nguyen
2013-03-04 4:18 ` mark.d.witmer
2013-03-04 4:38 ` mark.d.witmer
2013-03-04 10:02 ` Thien-Thi Nguyen [this message]
2013-03-03 10:36 ` Chris Vine
2013-03-04 13:29 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obezpjn1.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=mark.d.witmer@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).