Brett,
Thanks for the suggestion. Switching from socketpair() to
pipe() does let ssh get going, but rsync later runs into
problems. A few minutes into the transfer it just hangs.
Since I exercised ssh by transferring 16MB files back and
forth for 1
I've found an rsync problem that might be another data point for the
fork() (or exec()?) problems mentioned on the cygwin mailing list last
fall. On one of my systems rsync hangs after it forks a cygwin program.
Surprisingly, when it forks some native windows program, it completes.
I started this
On Mon, 25 Jul 2005 17:39:41 +0200, "Gerrit P. Haase" wrote:
>
> Indeed, I see no unsetenv() in the perl sources.
>
> Since it seems that the problem is independent of TH the problem should
> be located in perl itself. I'll try with a recent devel version to see
> if it fails here too. Scott, h
On Thu, 21 Jul 2005 00:14:51 -0700, Michael G Schwern wrote:
>
> Its gotta be something about _default_inc(). Nothing looks wrong from
> here. My only guess is that local $ENV{PERL5LIB} is ineffective. That
> would account for the alternation.
It's not just the local scoping. There is
On Tue, 19 Jul 2005 08:27:28 -0700, Michael G Schwern wrote:
> Try the same Test::Harness with an older perl. See if its a perl bug.
It is not a perl bug. It is something in the TH module.
I tested with perl 5.8.7 and the previous 5.8.6. I also,
through -I, tried both th
On Mon, 18 Jul 2005 01:50:33 -0700, Michael G Schwern wrote:
>
> MakeMaker is not involved, just Test::Harness. All the action is in or
> called from Test::Harness::Straps->analyze_file.
I agree. TH is resetting INC and the directories passed
into test_harness() are lost after th
Someone on this list mentioned it was possible to build a
native version of gvim using the cygwin sources. I've done
that and it's great, but I'm stumped on how to install it.
After I run (cd /usr/src/vim*/src; make -f Make_cyg.mak IME=yes)
I have a gvim.exe
>
> > It seems like cygwin syslog on w2k, both the logger command the
> > syslog(3) routine, works only for the SYSTEM account. Is that true?
>
> No. Perhaps the users privileges don't allow that? Members of the
> group "Users" (or the native analogon) have the appropriate permissions
> by defa
It seems like cygwin syslog on w2k, both the logger command the
syslog(3) routine, works only for the SYSTEM account. Is that true?
I have a test script that uses logger. When I call it manually no messages
appear in the event log. When I turn it into a service, where it is invoked
with SYSTEM pri
9 matches
Mail list logo
