Re: symlink problem

[Thomas Nikolajsen <thomas.nikolajsen@xxxxxxx>]

> :Using HEAD I sometime experience problem with symlink:
> :extra charactes after symlink destination. After some minutes this disappears.
> :
> : -thomas
> :-- 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
Only NFS.
>     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.
 15292 ls       CALL  readlink(0xbfbfeca0,0xbfbfe890,0x400)
 15292 ls       NAMI  "bin/uc"
 15292 ls       RET   readlink 1024/0x400
 15292 ls       CALL  write(0x1,0x880b8000,0x44)
 15292 ls       GIO   fd 1 wrote 68 bytes
       "lrwxr-xr-x  1 thomas  thomas  10 Apr  7 18:59 bin/uc -> update-cmd?
       "
Not too relevant anymore I guess; you already did solve problem.
This also solved buildworld problem I reported!
> 
> 					-Matt
> 					Matthew Dillon 
> 					<dillon@xxxxxxxxxxxxx>
 -thomas