public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: regulating the time a process can run with crontab?
Date: Fri, 28 Dec 2001 10:57:31 -0600	[thread overview]
Message-ID: <3.0.6.32.20011228105731.00987100@mail.doorpi.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0112281125420.999-100000@dave.private.mielke .cc>

Wow, will wget still work with these live streams that never end, or have
no definite size? In a background cron job, where will this status output
go, spam my email box? I don't think I need an email for every 50k, as this
process will run in the background. One problem I do have on dialup is that
the stream will stop, something would have to keep restarting it. Wouldn't
the until directive do it, or doesn't the until loop allow for the use of
time of day as a way to know when to stop restarting? One could use while
true or something and a second script to kill it off, but in practice,
infinite loops can go crazy and shouldn't be used.
At 11:27 AM 12/28/01 -0500, you wrote:
>It all depends on what you want your process to timeout for. If you want to
>protect against a hung connection, then a much better method is to download
>with wget rather than lynx. wget has just such a timeout option.
>
>-- 
>Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
>Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
>EMail: dave@mielke.cc | Canada  K2A 1H7   | if you're concerned about Hell.
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>




  parent reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Brent Harding
 ` Mike Gorse
   ` Brent Harding
     ` Dave Mielke
     [not found]     ` <Pine.LNX.4.30.0112281125420.999-100000@dave.private.mielke .cc>
       ` Brent Harding [this message]
 ` A. R. Vener
 ` James R. Van Zandt
   ` L. C. Robinson
     ` Brent Harding
       ` James R. Van Zandt
         ` L. C. Robinson
           ` Brent Harding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3.0.6.32.20011228105731.00987100@mail.doorpi.net \
    --to=bharding@doorpi.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).