[scponly] FreeBSD lost connection

[wbr oblyr]

actually,  there is some more debugging information that might prove
helpful.

if you could set your scponly debuglevel higher, like so:

echo 2 > /usr/local/etc/scponly/debuglevel

(unless you set the path to someplace else on setup)

scponly loads this file when it is launched and uses the contents to
determine how much diagnostic output to generate.

now, to capture the diagnostic output, you will need to do one of two
things:  either use the "log" feature in winscp to capture all output from
scponly OR use the commandline scp.

this should produce more valuable output, hopefully.

also, when you say:

On Wed, 4 Jun 2003, Feargal Reilly wrote:
> I've added an user 'test', set shell to /usr/local/bin/scponly, created
> homedir /home/test, chown'ed to test, set password. Added
> /usr/local/bin/scponly to /etc/shells, although I don't think it makes a
> difference.

when you say "chown'ed", do you mean run the setup_chroot.sh script?
"chown'ing" sounds more like you used the chown unix command, which
wouldnt make sense in the context yo used it...

let me know,
joe