DragonFly bugs List (threaded) for 2006-04
Re: symlink problem
:Using HEAD I sometime experience problem with symlink:
:extra charactes after symlink destination. After some minutes this disappears.
:-- on NFS mount: symlink dest. should be: net-bps
:$ ls -la bin/net
:lrwxr-xr-x 1 thomas thomas 7 Nov 5 09:00 bin/net -> net-bps??U?AU?U?????E??????U??????*???Q??P?T??E??P(UP??????U??????U**U??U(U??U??U?T?*E??U?T?*U*UE?A??U*@U?
:varsym not enabled: vfs.varsym_enable: 0
Does this only occur with NFS or is it an issue with UFS too? Symlinks
were switched to VM backing store in the kernel, a \0 termination
bug could have creeped in there.
If you could, when you see this problem, run your ls test under ktrace
and post the ktrace output. Specifically, I want to see what the
return value of the readlink system call is in the above case.