public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "A. R. Vener" <salt@aero-vision.com>
To: blinux-list@redhat.com
Subject: Re: regulating the time a process can run with crontab?
Date: Fri, 28 Dec 2001 09:16:36 -0500	[thread overview]
Message-ID: <20011228091636.A3554@cougar.aero-vision.com> (raw)
In-Reply-To: <3.0.6.32.20011227225916.0082e9d0@mail.doorpi.net>; from bharding@doorpi.net on Thu, Dec 27, 2001 at 10:59:16PM -0600

You use a separate script which sends a kill signal to
lynx. This would call a script that either looks up the pid
of your lynx process or identifies it from your original script.

For example the first line in your script could be:
echo $$ > $HOME/.recordingpid


the second script would execute:

kill -9 `cat $HOME/.recordingpid`

Rudy

On Thu, Dec 27, 2001 at 10:59:16PM -0600, Brent Harding wrote:
> 	Suppose I want to use the lynx --source option to record an mp3 stream
> that will start at a certain time, and I want to stop it at a certain time.
> I could start it with a cron entry, in a script, but how in such a script
> would I cause lynx to terminate, assuming the mp3 stream never quits?
> There's no way of telling lynx --source how much to get if this is in the
> background.
> Thanks.
> 
> 
> 
> 
> _______________________________________________
> 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
 ` A. R. Vener [this message]
 ` 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=20011228091636.A3554@cougar.aero-vision.com \
    --to=salt@aero-vision.com \
    --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).