GNU bug report logs - #29475
filesystem does not allow ln to create bad symbolic link

Previous Next

Package: coreutils;

Reported by: bug-coreutils <at> trodman.com

Date: Mon, 27 Nov 2017 18:28:01 UTC

Severity: normal

Tags: notabug

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #14 received at 29475 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: bug-coreutils <at> trodman.com, 29475 <at> debbugs.gnu.org
Subject: Re: bug#29475: filesystem does not allow ln to create bad symbolic
 link
Date: Mon, 27 Nov 2017 18:41:12 -0800
bug-coreutils <at> trodman.com wrote:
> stat("badlink", 0x7ffc0eb805a0)         = -1 ENOENT (No such file or directory)
> symlink("not-there", "badlink")         = -1 ENOENT (No such file or directory)

My guess is that you've removed the working directory somehow, or are on a buggy 
filesystem that thinks the working directory has been removed. I can reproduce 
the situation as follows on Ubuntu 16.04.3:

$ cd /tmp
$ mkdir d
$ cd d
$ rmdir /tmp/d
$ LC_ALL=C strace ln -s a b
...
stat("b", 0x7fffe6df6140)               = -1 ENOENT (No such file or directory)
symlink("a", "b")                       = -1 ENOENT (No such file or directory)
...

The only suggestion I have is "don't do that". If memory serves, POSIX doesn't 
specify the behavior in this case.




This bug report was last modified 6 years and 288 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.