Using shlight on 1.6 from both a sparc and i386 machine worked fine until I 
tried to do "real" work; meaning that touching a file on the share was ok 
and re-directing the output of man cdparanoia to the shared folder worked 
but using the shared folder as the destination of the cdparanoia data 
didn't work.  The files didn't get any bigger and I eventually rebooted the 
NetBSD machine.

At 01:29 PM 10/29/2002 -0800, Jeremy C. Reed wrote:
>I mounted a remote SMB share with:
>  /usr/pkg/sbin/shlight '//heather/shared' /windows -s win98
>
>(This is sharity-light-1.2 under NetBSD/i386 1.6.)
>
>I couldn't see any files in the share until I locally added a file:
>"touch J". Then I could see the other files. Even when I copied new
>files to the share on the remote end, my NetBSD side wouldn't see them
>(until I touched a file locally on the NetBSD side).
>
>This seems different that when I used rumba over a year ago. Any ideas?
>
>When trying to read some files from the share with sylpheed (it was
>sending as attachments), sylpheed just hung in a "D" (process in disk
>or uninterruptable) state. I couldn't kill sylpheed.
>I tried to do a ls of / and ls hung. Anything that accessed /windows
>would hang in the "D" state.
>
>I couldn't kill shlight and "unshlight -a" hung too.
>I did see some nfsiod threads which I could kill.
>
>36 hours later some of the processes finally were killed
>on their own.
>
>Any suggestions on how I can trace what is happening with that running
>unshlight and shlight?
>
>$ ktrace -p 4224
>$ kdump
>   4224 shlight  EMUL  "netbsd"
>
>Anyone successfully using shlight?
>
>    Jeremy C. Reed
>    http://bsd.reedmedia.net/