From 32e789ff44de2ce90665230a3f4c3e2f7cb01067 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 30 Jul 2010 15:43:43 +0200 Subject: open_issues/bash_interrupted_system_call: New. --- open_issues/bash_interrupted_system_call.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 open_issues/bash_interrupted_system_call.mdwn diff --git a/open_issues/bash_interrupted_system_call.mdwn b/open_issues/bash_interrupted_system_call.mdwn new file mode 100644 index 00000000..9feab6ff --- /dev/null +++ b/open_issues/bash_interrupted_system_call.mdwn @@ -0,0 +1,19 @@ +[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +IRC, unknown channel, unknown date. + + i seem to be getting this message from the shell "-bash: /dev/fd/62: Interrupted system call" + is it significant ? + I've seen this issue already yes + it's not + it's bash not handling EINTR properly + youpi: so this is actually a bug in bash, not Hurd generating a bogus error? + well, it's Hurd generating an error which bash doesn't expect to see -- cgit v1.2.3