path: root/open_issues/open_symlink.mdwn
diff options
authorSamuel Thibault <>2015-02-18 00:58:35 +0100
committerSamuel Thibault <>2015-02-18 00:58:35 +0100
commit49a086299e047b18280457b654790ef4a2e5abfa (patch)
treec2b29e0734d560ce4f58c6945390650b5cac8a1b /open_issues/open_symlink.mdwn
parente2b3602ea241cd0f6bc3db88bf055bee459028b6 (diff)
Revert "rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn"
This reverts commit 95878586ec7611791f4001a4ee17abf943fae3c1.
Diffstat (limited to 'open_issues/open_symlink.mdwn')
1 files changed, 30 insertions, 0 deletions
diff --git a/open_issues/open_symlink.mdwn b/open_issues/open_symlink.mdwn
new file mode 100644
index 00000000..663bfcbd
--- /dev/null
+++ b/open_issues/open_symlink.mdwn
@@ -0,0 +1,30 @@
+[[!meta copyright="Copyright © 2012, 2013 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
+[[!tag open_issue_glibc]]
+# IRC, freenode, #hurd, 2012-01-02
+ <pinotree> hm, is it a known issue that open("somesymlink", O_RDONLY |
+ O_NOFOLLOW) does not fail with ELOOP?
+ <youpi> pinotree: iirc there is code for it, maybe not the same behavior as
+ on linux
+## IRC, OFTC, #debian-hurd, 2013-05-08
+ <pinotree> the hurd issue is that O_NOFOLLOW seems broken on symlinks, and
+ thus open(symlink, O_NOFOLLOW) doesn't fail with ELOOP
+ <youpi> I don't really see why it should fail
+ <youpi> since NOFOLLOW says not to follow the symlink
+ <pinotree> yeah, but you cannot open a symlink
+ <youpi> ah right ok
+ <youpi> interesting :)