DragonFlyBSD

Just some more discoverings. When you login via ssh, and you issue:

[vmware] ~> ps axl | grep tcsh
1000 959 958 8 152 0 3688 1720 ppwait DLs 0 0:00.04 -tcsh (tcsh)
1000 965 959 8 157 0 3688 1720 - RVL 0 0:00.00 -tcsh (tcsh)

See that tcsh in ppwait wchan is child of sshd:

1000   958   956   0 152   0  7904 2452 kqread SL    ??    0:00.02 sshd:
antonioh@pts/0 (sshd)

And the tcsh process in RVL state is child of the other tcsh. If you issue
several ps command again and again, you'll see that tcsh process PID changes.

[vmware] ~> ps axl | grep tcsh
1000 959 958 8 152 0 3688 1720 ppwait DLs 0 0:00.06 -tcsh (tcsh)
1000 974 959 8 157 0 3688 1720 - RVL 0 0:00.00 -tcsh (tcsh)
[vmware] ~> ps axl | grep tcsh
1000 959 958 9 152 0 3688 1720 ppwait DLs 0 0:00.06 -tcsh (tcsh)
1000 976 959 9 157 0 3688 1720 - RVL 0 0:00.00 -tcsh (tcsh)
[vmware] ~> ps axl | grep tcsh
1000 959 958 9 152 0 3688 1720 ppwait DLs 0 0:00.06 -tcsh (tcsh)
1000 978 959 9 157 0 3688 1720 - RVL 0 0:00.00 -tcsh (tcsh)
[vmware] ~> ps axl | grep tcsh
1000 959 958 10 153 0 3688 1720 ppwait DLs 0 0:00.06 -tcsh (tcsh)
1000 980 959 10 158 0 3688 1720 - RVL 0 0:00.00 -tcsh (tcsh)

Ok, this should be fixed by 470b5de8bab672e9f29c78eb9f41807d3310fa3d
now.

-Matt