Re: Small test example for: cannot create /dev/null: Interrupted system call

To: Svante Signell <svante.signell@gmail.com>
Cc: bug-hurd <bug-hurd@gnu.org>, debian-hurd <debian-hurd@lists.debian.org>
Subject: Re: Small test example for: cannot create /dev/null: Interrupted system call
From: Richard Braun <rbraun@sceen.net>
Date: Thu, 10 Jul 2014 23:26:24 +0200
Message-id: <[🔎] 20140710212624.GA20634@dalaran.sceen.net>
In-reply-to: <[🔎] 20140710211817.GA18372@dalaran.sceen.net>
References: <[🔎] 1404732560.18216.33.camel@G3620.my.own.domain> <[🔎] 20140710211817.GA18372@dalaran.sceen.net>

On Thu, Jul 10, 2014 at 11:18:17PM +0200, Richard Braun wrote:
> All right, it looks like open() gets interrupted by SIGCHLD here. It's
> my understanding that signal handling is highly system-specific in such
> cases, but we probably want to align on what others do, as usual.

By the way, it looks like it happens with dash only, not bash. I suppose
dash relies on the Linux-specific behaviour of interrupting a blocked
open(). See if switching to bash helps.

-- 
Richard Braun

Reply to:

Follow-Ups:
- Re: Small test example for: cannot create /dev/null: Interrupted system call
  - From: Thomas Schwinge <thomas@codesourcery.com>

References:
- Small test example for: cannot create /dev/null: Interrupted system call
  - From: Svante Signell <svante.signell@gmail.com>
- Re: Small test example for: cannot create /dev/null: Interrupted system call
  - From: Richard Braun <rbraun@sceen.net>

Prev by Date: Re: Small test example for: cannot create /dev/null: Interrupted system call
Next by Date: Re: Small test example for: cannot create /dev/null: Interrupted system call
Previous by thread: Re: Small test example for: cannot create /dev/null: Interrupted system call
Next by thread: Re: Small test example for: cannot create /dev/null: Interrupted system call
Index(es):
- Date
- Thread