To: cygwin@cygwin.com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r.berber@computer.org>
Subject:  Re: cygrunsrv autossh - tunnel does not come up
Date:  Fri, 09 Jan 2009 11:47:00 -0600
Lines: 22
Message-ID: <gk82i1$cd8$1@ger.gmane.org>
References:  <21362436.post@talk.nabble.com> <gk65nu$nqh$1@ger.gmane.org> <5uaem4hkujkube83ulle0s8fsm93mghahi@4ax.com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1
Content-Transfer-Encoding:  quoted-printable
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
In-Reply-To: <5uaem4hkujkube83ulle0s8fsm93mghahi@4ax.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Andrew Schulman wrote:

> Hm, I'm surprised to hear that.  I haven't run autossh as a service in a =
while,
> but when I did it worked very reliably for me.  Can you tell me anything =
more
> about how or why it fails to start?

No, sorry, there's no useful information on the events or on any log; I
just start it manually when it fails.

My guess is that since networking is very slow to get started on my
computer, and that's a feature of my network card / driver (I can see
the link go up on the switch long after boot up, after Windows starts in
fact, about when the login window appears) and the service dependency
doesn't help (that's a feature of Windows, it probably is starting the
service before the network is really up) the first logon attempt fails
and somehow autossh gives up, after bootup it behaves as it should
reestablishing the connection when lost, but not on first start, that's
why I guess the network is not really up and that makes the difference.
--=20
Ren=E9 Berber


--
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/