[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: confusing error message from ln
From: |
Bob Proulx |
Subject: |
Re: confusing error message from ln |
Date: |
Fri, 28 Oct 2005 09:49:44 -0600 |
User-agent: |
Mutt/1.5.9i |
Andreas Schwab wrote:
> Bob Proulx writes:
> > I like this suggestion of yours. I agree that the symlink value
> > cannot be a source of error.
>
> It can, when it is too long.
Yes, you are correct. The limit is 3976 characters on my system with
a reiserfs filesystem. I ran the following script to test this.
value=x
while rm -f /tmp/symlinktest ; ln -s $value /tmp/symlinktest; do
value=x$value
done
echo at $(printf $value | wc -c) characters
After about ten seconds it produced the following output, with 3967
'x' characters deleted and replaced with "..." so that it would not be
too much of a waste of bandwidth in this message.
ln: creating symbolic link `/tmp/symlinktest' to `xxxxx...xxxxx': File name
too long
at 3977 characters
Bob
- confusing error message from ln, Elan Ruusamäe, 2005/10/27
- Re: confusing error message from ln, Bob Proulx, 2005/10/28
- Re: confusing error message from ln, Andreas Schwab, 2005/10/28
- Re: confusing error message from ln,
Bob Proulx <=
- Re: confusing error message from ln, Paul Eggert, 2005/10/28
- Re: confusing error message from ln, Bob Proulx, 2005/10/30
- Re: confusing error message from ln, Paul Eggert, 2005/10/30
- Re: confusing error message from ln, Bob Proulx, 2005/10/30
- Re: confusing error message from ln, Paul Eggert, 2005/10/31