public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Dube <mathieu_dube@videotron.ca>
To: linux-kernel@vger.kernel.org
Cc: acahalan@cs.uml.edu
Subject: Re: accept
Date: Sun, 4 Feb 2001 11:40:55 -0500	[thread overview]
Message-ID: <01020411423601.00110@grndctrl> (raw)
In-Reply-To: <200102040044.f140i7a473095@saturn.cs.uml.edu>
In-Reply-To: <200102040044.f140i7a473095@saturn.cs.uml.edu>

On Sat, 03 Feb 2001, you wrote:
> > What does it typically mean when accept returns 0
> > and that the perror outputs "Interupted system call"??
> 
> During the call, your process received a signal.
> Most system calls are affected in this way, so that
> you may break out of what you are doing by sending
> a signal to yourself with alarm().
> 
> It sucks too, since you have to wrap nearly every
> system call in a while loop. You can avoid some of
> the trouble with careful use of sigaction() to make
> the OS restart system calls in some conditions.
Could it be the SIG32 signal that pthreads use ??
-- 
Mathieu Dube
Mondo-Live
-
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:[~2001-02-04 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200102040044.f140i7a473095@saturn.cs.uml.edu>
2001-02-04 16:40 ` Mathieu Dube [this message]
2001-02-04 18:00 accept W1012
  -- strict thread matches above, loose matches on Subject: below --
2001-02-04  0:42 accept Mathieu Dube
2001-02-04 11:01 ` accept David Schwartz
2001-02-04 16:37   ` accept Mathieu Dube
2001-02-04 20:27     ` accept J . A . Magallon
2001-02-05  0:14     ` accept David Schwartz
2001-02-05 12:59     ` accept Richard B. Johnson

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=01020411423601.00110@grndctrl \
    --to=mathieu_dube@videotron.ca \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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