On Tue, 2005-09-13 at 04:34 -0700, Brandin Creech wrote:
> Have you tried the ConnectTimeout option? It may be what you need. However,
> maybe not; I checked ssh_config(5) for details and it says that the timeout
> value is only used if the host is unreachable.
Yeah, that's the problem. ConnectTim
--- Simon Geard <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-09-12 at 12:00 -0700, Brandin Creech wrote:
> > Here is a generic method to implement a timeout in BASH.
>
> Looks good - I use something similar at work to scp a file to a bunch of
> other machines from a cron job.
> pid=$! #pid of last
On Mon, 2005-09-12 at 12:00 -0700, Brandin Creech wrote:
> Here is a generic method to implement a timeout in BASH. Suppose you have a
> script that potentially takes a long time to execute. Such a script looks
> like this:
Looks good - I use something similar at work to scp a file to a bunch of
o
> Here is a generic method to implement a timeout in BASH.
>SNIP<
NICE! *applause*
Dave
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
--- HAUTZ Gilles <[EMAIL PROTECTED]> wrote:
> Andrew Benton a écrit :
>
> > HAUTZ Gilles wrote:
> >
> >> Hi all,
> >>
> >> I've discovered a "bug" in the ntp boot script.
> >> If there is no network connectivity or a DNS problem. The computer
> >> won't boot and stay at NTP starting.
> >
> > May
I think the timeout is the best solution, but how to implement that with
the bootscript ?
Andrew Benton a écrit :
HAUTZ Gilles wrote:
Hi all,
I've discovered a "bug" in the ntp boot script.
If there is no network connectivity or a DNS problem. The computer
won't boot and stay at NTP starti
HAUTZ Gilles wrote:
Hi all,
I've discovered a "bug" in the ntp boot script.
If there is no network connectivity or a DNS problem. The computer won't
boot and stay at NTP starting.
I think we should first check that we can reach the ntp server before
trying to start ntpd.
I know that RH try fir
