summaryrefslogtreecommitdiff
path: root/open_issues/bash_interrupted_system_call.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/bash_interrupted_system_call.mdwn')
-rw-r--r--open_issues/bash_interrupted_system_call.mdwn19
1 files changed, 0 insertions, 19 deletions
diff --git a/open_issues/bash_interrupted_system_call.mdwn b/open_issues/bash_interrupted_system_call.mdwn
deleted file mode 100644
index 9feab6ff..00000000
--- a/open_issues/bash_interrupted_system_call.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!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.
-
- <virtuoso015> i seem to be getting this message from the shell "-bash: /dev/fd/62: Interrupted system call"
- <virtuoso015> is it significant ?
- <youpi> I've seen this issue already yes
- <youpi> it's not
- <youpi> it's bash not handling EINTR properly
- <antrik> youpi: so this is actually a bug in bash, not Hurd generating a bogus error?
- <youpi> well, it's Hurd generating an error which bash doesn't expect to see