GNU bug report logs -
#13447
ln "" foo gives misleading error message
Previous Next
Reported by: Ken Irving <ken.irving <at> alaska.edu>
Date: Tue, 15 Jan 2013 08:32:01 UTC
Severity: normal
Tags: notabug
Done: Bob Proulx <bob <at> proulx.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
(Previously sent in error to the bug-gnu-utils list.)
I've been using symbolic links in a non-file-related way, e.g., to store
arbitrary string values, but find that if I try to create a symlink with
an empty 'target' name, e.g., as 'ln -s "" foo', the error message emitted
is not really correct.
$ ln -s "" foo
ln: creating symbolic link `foo' -> `': No such file or directory
$ ln -sf "" foo
ln: creating symbolic link `foo' -> `': No such file or directory
A link can be created when no file or directory exists, e.g.,
$ stat x || ln -s x foo && echo ok
stat: cannot stat `x': No such file or directory
ok
so it seems that 'No such file or directory' must not be the actual
reason for the failure. Perhaps something like 'null target name'
would be more accurate?
I only happened upon this in working on a test script, and have no
expectation for the operation to succeed.
Thanks
Ken Irving
This bug report was last modified 12 years and 188 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.