Setup fails to write help output to logfile [was RE: 1.5.12 ssh hangs on some machines when stdout has content]

[Dave Korn]

Rolf Campbell wrote:
> Igor Pechtchanski wrote:
>> As I've said before, .
>> This result from the search I suggested looks promising, if only to get
>> the setup options: .  See
>> also /var/log/setup.log after "setup --help" (yes, it does support this).
>> HTH,
> 
> I mostly don't see any output from "setup --help".  

  What does this have to do with ssh?  Subject line changed!

> I tried deleting the
> setup log files from /var/log and ran "setup --help", but no files were
> created in "/var/log".  It also doesn't work if the files exist.  I'm
> pretty sure it's not a permission problem cause if I run setup without
> any arguments it creates the log files just fine.  The weirdest thing is
> that it worked once for me about 10 minutes ago.  I'm running version
> 2.510.2.2.

  Bizarre, so it does.  According to my tests, it now appears to be writing
setup.log to whatever is the current directory when you run it.  Oops, this
looks like a real bug!  Now investigating ...


  BTW, here's the help info, just FYI:

2005/10/25 17:32:27 Starting cygwin install, version 2.510.2.2
2005/10/25 17:32:27 Current Directory: C:\cygwin.src
2005/10/25 17:32:27 
Command Line Options:
 -D --download  Download from internet
 -L --local-install Install from local directory
 -s --site  Download site
 -R --root  Root installation directory
 -q --quiet-modeUnattended setup mode
 -h --help  print help
 -l --local-package-dir Local package directory
 -r --no-replaceonrebootDisable replacing in-use files on
next
reboot.
 -n --no-shortcuts  Disable creation of desktop and
start
menu shortcuts
 -N --no-startmenu  Disable creation of start menu
shortcut
 -d --no-desktopDisable creation of desktop shortcut
 -A --disable-buggy-antivirus   Disable known or suspected buggy
anti
virus software packages during
execution.
Ending cygwin install


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.12 ssh hangs on some machines when stdout has content

[Rolf Campbell]

Igor Pechtchanski wrote:

As I've said before, .
This result from the search I suggested looks promising, if only to get
the setup options: .  See
also /var/log/setup.log after "setup --help" (yes, it does support this).
HTH,


I mostly don't see any output from "setup --help".  I tried deleting the 
setup log files from /var/log and ran "setup --help", but no files were 
created in "/var/log".  It also doesn't work if the files exist.  I'm 
pretty sure it's not a permission problem cause if I run setup without 
any arguments it creates the log files just fine.  The weirdest thing is 
that it worked once for me about 10 minutes ago.  I'm running version 
2.510.2.2.



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.12 ssh hangs on some machines when stdout has content

[Igor Pechtchanski]

On Tue, 25 Oct 2005, David Corbin wrote:

> On Tuesday 25 October 2005 10:12, Igor Pechtchanski wrote:
> > On Tue, 25 Oct 2005, David Corbin wrote:
>
> > The first thing anyone would notice is that 1.5.12 (and your
> > OpenSSH/OpenSSL versions) are very old.  The current Cygwin is 1.5.18
> > (going on 1.5.19), and OpenSSH is up to 4.2p1.  This list cannot afford to
> > support more than the current version of Cygwin and tools.  If you can
> > still reproduce your problem after upgrading to the latest versions of
> > Cygwin and OpenSSH/OpenSSL, please report back to this list.
>
> I will give it a try, but we do have a rather large set (~1 systems
> in over 500 locations) that would need to be upgraded.

Initially, you only need to try this on one system that exhibits the
problem...

> Is there any direct/easy way to upgrade cygwin without user-interaction?
> The only way I know is to run the GUI install program, and that's going
> to be a big problem for us.

As I've said before, .
This result from the search I suggested looks promising, if only to get
the setup options: .  See
also /var/log/setup.log after "setup --help" (yes, it does support this).
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.12 ssh hangs on some machines when stdout has content

[Chris Taylor]

David Corbin wrote:
I will give it a try, but we do have a rather large set (~1 systems in 
over 500 locations) that would need to be upgraded.  Is there any direct/easy 
way to upgrade cygwin without user-interaction?  The only way I know is to 
run the GUI install program, and that's going to be a big problem for us.


Thanks
David



Yes. Upgrade one machine, and build an msi that updates the files, then 
distribute it via active directory.

Alternatively, use your preferred packaging format.

Failing that, update a machine, zip up the updated cygwin folder, and 
distribute it across your network onto each machine, using administrator 
rights to stop the ssh service before applying.


I should point out that there is no guarantee that permissions would 
remain intact with either method.



Chris

--

Spinning complacently in the darkness, covered and blinded by a blanket
of little lives, false security has lulled the madness of this world
into a slumber. Wake up! An eye is upon you, staring straight down and
keenly through, seeing all that you are and everything that you will
never be. Yes, an eye is upon you, an eye ready to blink. So face
forward, with arms wide open and mind reeling. Your future has
arrived... Are you ready to go?

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.12 ssh hangs on some machines when stdout has content

[David Corbin]

On Tuesday 25 October 2005 10:12, Igor Pechtchanski wrote:
> On Tue, 25 Oct 2005, David Corbin wrote:

> The first thing anyone would notice is that 1.5.12 (and your
> OpenSSH/OpenSSL versions) are very old.  The current Cygwin is 1.5.18
> (going on 1.5.19), and OpenSSH is up to 4.2p1.  This list cannot afford to
> support more than the current version of Cygwin and tools.  If you can
> still reproduce your problem after upgrading to the latest versions of
> Cygwin and OpenSSH/OpenSSL, please report back to this list.

I will give it a try, but we do have a rather large set (~1 systems in 
over 500 locations) that would need to be upgraded.  Is there any direct/easy 
way to upgrade cygwin without user-interaction?  The only way I know is to 
run the GUI install program, and that's going to be a big problem for us.

Thanks
David

>
> FWIW, I regularly use just such a construct to reply to email -- I used it
> to reply to yours, and, as you can see, it
> .
> HTH,
>   Igor

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.12 ssh hangs on some machines when stdout has content

[Igor Pechtchanski]

On Tue, 25 Oct 2005, David Corbin wrote:

> I have found that ssh hangs semi-consistently, when it's stdout is piped
> to another process.
>
> I say semi-consistently, because it's not happening on all of our
> machines, but it is consistent for any of the problem machines.
> Furthermore, the command must actually produce output to standard out.
> The remote command is actually finishing, and as a far as I can tell, is
> terminating cleanly and correctly.
>
> Here is an easy way to reproduce it:
>
> ssh [EMAIL PROTECTED] ls -a | wc -l
>
> The following work fine:
>
> ssh [EMAIL PROTECTED] ls -a
> ssh [EMAIL PROTECTED] ls -a >/dev/null
>
> My cygcheck.out file is attached.  ssh reports it's version as SSH
> version OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004
>
> The destination host does not appear to matter (I've tested against
> cygwin-sshd, and a linux box).
>
> This has my very baffled, and concerned.  Any help appreciated.

The first thing anyone would notice is that 1.5.12 (and your
OpenSSH/OpenSSL versions) are very old.  The current Cygwin is 1.5.18
(going on 1.5.19), and OpenSSH is up to 4.2p1.  This list cannot afford to
support more than the current version of Cygwin and tools.  If you can
still reproduce your problem after upgrading to the latest versions of
Cygwin and OpenSSH/OpenSSL, please report back to this list.

FWIW, I regularly use just such a construct to reply to email -- I used it
to reply to yours, and, as you can see, it
.
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: 1.5.12 ssh hangs on some machines when stdout has content

[Dave Korn]

David Corbin wrote:
> I have found that ssh hangs semi-consistently, when it's stdout is piped
> to another process.
> 
> I say semi-consistently, because it's not happening on all of our
> machines, but it is consistent for any of the problem machines. 
> Furthermore, the command must actually produce output to standard out. 
> The remote command is actually finishing, and as a far as I can tell, is
> terminating cleanly and correctly.
> 
> Here is an easy way to reproduce it:
> 
> ssh [EMAIL PROTECTED] ls -a | wc -l

  WJFFM.

> This has my very baffled, and concerned.  Any help appreciated.

  1.5.12 is quite old.  Try upgrading or even have a go with the current
development snapshot (http://cygwin.com/snapshots) - it's in a testing cycle
at the moment and it would be helpful to know if your problem is fixed (see
also http://cygwin.com/ml/cygwin/2005-09/msg01020.html)


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/