linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmail.virusscreen.com>
To: George Talbot <george@brain.moberg.com>,
	"Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Tim Hockin <thockin@isunix.it.ilstu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land
Date: Mon, 6 Nov 2000 16:30:03 +0100	[thread overview]
Message-ID: <00110616325700.00204@linux1.home.bogus> (raw)
In-Reply-To: <Pine.LNX.4.21.0011060824000.4984-100000@brain.moberg.com>
In-Reply-To: <Pine.LNX.4.21.0011060824000.4984-100000@brain.moberg.com>

On Mon, 06 Nov 2000, George Talbot wrote:
> On Fri, 3 Nov 2000, Theodore Y. Ts'o wrote:
> 
> >    Date: 	Fri, 03 Nov 2000 14:44:17 -0500
> >    From: george@moberg.com
> > 
> >    My problem is that pthread_create (glibc 2.1.3, kernel 2.2.17 i686) is
> >    failing because, deep inside glibc somewhere, nanosleep() is returning
> >    EINTR.
> > 

I've lost previous messages but have You tried :

man siginterrupt


- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-06 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200011031841.MAA07209@isunix.it.ilstu.edu>
2000-11-03 19:44 ` Can EINTR be handled the way BSD handles it? -- a plea from a user-land george
2000-11-03 21:27   ` H. Peter Anvin
2000-11-04  4:23   ` Theodore Y. Ts'o
2000-11-06 14:05     ` George Talbot
2000-11-06 15:30       ` Davide Libenzi [this message]
2000-11-06 17:50       ` Can EINTR be handled the way BSD handles it? -- a plea from a Tim Hockin
2000-11-06 14:17     ` Can EINTR be handled the way BSD handles it? -- a plea from a user-land George Talbot

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=00110616325700.00204@linux1.home.bogus \
    --to=davidel@xmail.virusscreen.com \
    --cc=george@brain.moberg.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@isunix.it.ilstu.edu \
    --cc=tytso@MIT.EDU \
    /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).