Dirk Herrmann <[EMAIL PROTECTED]> writes:
> When I use the following wrapper file:
> #!/bin/bash
> lsh --debug $* 2>lsh.errlog
> then everything works. If I use lsh directly, it doesn't. Thus, it seems
> that I can't provide useful information this way :-(
That's bad. Does it matter if you direct stderr to a file or to
/dev/null? (If lsh works better with stderr to /dev/null, at least
that's an ugly workaround for the problem).
> I don't know which kind of service could be tried this way. The only
> thing I am using is cvs. Maybe Jeff Bailey could make some suggestions
> about some simple thing that may be run this way...
Someone else reported that something similar happens if you create a
directory with a few thousand files in it, and then execute ls -l over
lsh. The first data that is lost is located about 128k from the start
of the ls output. I'll try to track it down.
/Niels
