From: whitnl73@juno.com
To: p.howell74@rcn.com
Cc: linux-newbie@vger.kernel.org
Subject: Re: scripting the "rec" function for a fixed time.
Date: Fri, 7 Mar 2003 19:22:48 -0500 (EST) [thread overview]
Message-ID: <20030307.192525.8.1.whitnl73@juno.com> (raw)
In-Reply-To: <1046131264.10885.28.camel@smeagle>
On 24 Feb 2003, Peter Howell wrote:
> I would like to be able to run the rec command unattended. Right now
> when executed, it will record sound until I hit C-c. I would really
> like to be able to right a script which will execute "rec ...", then
> wait a specified period of time, then pass the C-c to it. Or is there a
> simpler way?
>
> Thanks
>
> Peter
I don't have rec or any hardware to do with sound, so I'll use "yes"
to demonstrate a program that runs until interrupted. Not I use SIGHUP
rather than SIGINT, as bash provides a handler for SIGINT for background
jobs. stdout and stderr don't have to be null, but they have to be
directed away from the terminal.
#!/bin/sh
yes >/dev/null 2>/dev/null &
sleep 1
kill -HUP $!
Lawson
--
---oops---
________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2003-03-08 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 0:01 scripting the "rec" function for a fixed time Peter Howell
2003-02-25 2:55 ` Ray Olszewski
2003-02-25 6:14 ` pa3gcu
2003-02-26 0:44 ` Peter Howell
2003-02-26 6:01 ` pa3gcu
2003-02-26 8:08 ` Elias Athanasopoulos
2003-02-26 10:19 ` Carl
2003-02-26 17:26 ` Eric
2003-02-25 7:01 ` Elias Athanasopoulos
2003-03-08 0:22 ` whitnl73 [this message]
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=20030307.192525.8.1.whitnl73@juno.com \
--to=whitnl73@juno.com \
--cc=linux-newbie@vger.kernel.org \
--cc=p.howell74@rcn.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