Jonathan Dowland wrote:
> On Sun, Nov 03, 2013 at 09:58:58PM +0100, Erwan David wrote:
>> Maybe you'll need something like expect to handle this.
> I'd second expect, it's probably the best tool for the job in all
> non-trivial cases.
The "empty-expect" package, perhaps?
Chris
--
To UNSUBSCRI
On 11/4/13, Thomas H. George wrote:
> The script I am trying to write executes a program that requires a
> keyboard response. I have experimented with redirecting STDIN but haven't
> found the
> correct way to make the response.
To read a value (perhaps half your "problem"):
apt-cache show ...
z
Hi
On Sun, Nov 03, 2013 at 02:35:30PM -0500, Thomas H. George wrote:
> The script I am trying to write executes a program that requires a
> keyboard response. I have experimented with redirecting STDIN but haven't
> found the
> correct way to make the response. I found one example that scanned t
The tool 'yes' can be used to write an infinite stream of strings
(the default being 'y') to standard output, so if your program needed
only a sequence of a fixed string such as 'y', you could do
> yes | your-program
or
> yes "some-other-string" | your-program
But if your program is not readin
Le 03/11/2013 20:35, Thomas H. George a écrit :
> The script I am trying to write executes a program that requires a
> keyboard response. I have experimented with redirecting STDIN but haven't
> found the
> correct way to make the response. I found one example that scanned the
> response from apt
> The script I am trying to write executes a program
> that requires a keyboard response.
>
A varaible can be set to a keyboard response
using a read prompt
read -e -p "What do you need ?" xVariable
echo $xVariable
--
Stanley C. Kitching
Human Being
Phoenix, Arizon
Here's something I modified as part of a benchmark script called "fdtree".
--
Karl Vogel I don't speak for the USAF or my company
Dijkstra probably hates me. --Linus Torvalds, in kernel/sched.c
#!/bin/bash
# How to use xdate/xtime/persec:
#
# START=$(date "+%s")
On 2010-03-29 16:35, Mike McClain wrote:
[snip]
Thanks a lot. Though my error was pointed out as a typo and corrected
a while back your solution using " date '+%s' " is much more elegant
than what I had done.
If you want more (possibly too much) precision:
$ date +'%s.%N'
--
"History does not
Hi Josep,
On Mon, Mar 29, 2010 at 02:28:20PM +0200, Josep M. wrote:
>
> I found these somewhere time ago. check if is what You need:
>
Thanks a lot. Though my error was pointed out as a typo and corrected
a while back your solution using " date '+%s' " is much more elegant
than what I had don
Hello.
I found these somewhere time ago. check if is what You need:
function timer()
{
if [[ $# -eq 0 ]]; then
echo $(date '+%s')
else
local stime=$1
etime=$(date '+%s')
if [[ -z "$stime" ]]; then stime=$etime; fi
dt=$((etime - stime)
Paul E Condon wrote:
Try:
bgn=$(date +%s)
sleep 7
end=$(date +%s)
echo "elapsed seconds = " $(( end - bgn ))
You might also want to experiment with:
ps h -o etime $$
as long as you're happy with it only running under gnu. Prints the
elapsed time for the shell.
--
Chris Jackson
Shadowcat
On 20100319_101928, Mike McClain wrote:
> I've written a function to print elapsed time similar to /usr/bin/time
> but can be called at the beginning and end of a script from within
> the script. Occasionally I get an error: '8-08: value too great for base'
> It's caused by the difference in these
On Fri, Mar 19, 2010 at 06:45:15PM +0100, Sven Joachim wrote:
> On 2010-03-19 18:19 +0100, Mike McClain wrote:
>
> > I've written a function to print elapsed time similar to /usr/bin/time
> > but can be called at the beginning and end of a script from within
> > the script. Occasionally I get an e
On Fri, Mar 19, 2010 at 10:19:28AM -0700, Mike McClain wrote:
typo right herevv
> now='09:07:16'; startHr=${now%%:*}; startHR=${startHr#*0}; echo $startHr;
Apologies for troubling all.
Mike (with egg on face)
--
Satisfied user of Linux since 1997.
O< ascii ribbon c
Mike McClain wrote:
I've written a function to print elapsed time similar to /usr/bin/time
but can be called at the beginning and end of a script from within
the script. Occasionally I get an error: '8-08: value too great for base'
It's caused by the difference in these 2 command strings but I ca
Mike McClain wrote:
I've written a function to print elapsed time similar to /usr/bin/time
but can be called at the beginning and end of a script from within
the script. Occasionally I get an error: '8-08: value too great for base'
It's caused by the difference in these 2 command strings but I c
On Fri, Mar 19, 2010 at 1:19 PM, Mike McClain wrote:
> I've written a function to print elapsed time similar to /usr/bin/time
> but can be called at the beginning and end of a script from within
> the script. Occasionally I get an error: '8-08: value too great for base'
> It's caused by the diffe
On 2010-03-19 18:19 +0100, Mike McClain wrote:
> I've written a function to print elapsed time similar to /usr/bin/time
> but can be called at the beginning and end of a script from within
> the script. Occasionally I get an error: '8-08: value too great for base'
> It's caused by the difference i
Tyler Smith wrote:
On 2007-05-17, Bob McGowan <[EMAIL PROTECTED]> wrote:
Some general comments, mostly aimed at making your code cleaner without
changing what it does.
First, both 'echo' and 'printf' put their results on standard out. Your
call of 'printf' is inside command substitution, so
On Thu, May 17, 2007 at 03:40:15AM +, Tyler Smith wrote:
> On 2007-05-17, Bob McGowan <[EMAIL PROTECTED]> wrote:
> >
> > Some general comments, mostly aimed at making your code cleaner without
> > changing what it does.
> >
> > First, both 'echo' and 'printf' put their results on standard out.
On 2007-05-17, Bob McGowan <[EMAIL PROTECTED]> wrote:
>
> Some general comments, mostly aimed at making your code cleaner without
> changing what it does.
>
> First, both 'echo' and 'printf' put their results on standard out. Your
> call of 'printf' is inside command substitution, so its STDOUT
Tyler Smith wrote:
Hi,
I've got a question about a short bash script I wrote. I need it to
--snipped--
#!/bin/bash
lab_num=41
for map_name in aest_90 bush_90 carol_90 comp_90 \
hirs_90 roan_90 swan_90 vir_90 ;
do
lab_let=$(echo -n $(printf "\\x$(echo $lab_num)"))
echo "
$la
On 2007-05-16, Karl E. Jorgensen <[EMAIL PROTECTED]> wrote:
>> This was the only way I could figure out to loop from A to H. But
>> since it works on hex escape codes, it won't work past 9. Is there a
>> cleaner, more general way to do this?
>
> I think there is:
>
> #!/bin/bash
>
> ( cat < A aest_
On Wed, May 16, 2007 at 08:46:37PM +, Tyler Smith wrote:
> Hi,
>
> I've got a question about a short bash script I wrote. I need it to
> loop over a number of names, and pass a command to grass that includes
> two variations of those names. That was easy. Harder was getting
> getting a letter
On Fri, Sep 29, 2006 at 08:02:38AM -0500, Hugo Vanwoerkom wrote:
> Kevin Mark wrote:
> >On Wed, Sep 27, 2006 at 09:22:05PM -0500, Ron Johnson wrote:
> >>how about
> >> b=`$a`
> >> echo $b
> >
> >or
> >echo $($a)
>
>
> Bingo!!! Thanks!
> Is that in the Advanced Bash-Scripting Guide?
> H
>
Hi H
Hugo Vanwoerkom wrote:
Hi,
On my way to elapsed time in a bash script, I created the do_chrono
command. It pumps the elapsed time to stdout.
So if I do:
a=do_chrono
and then:
$a
I get: 0:3:19.
Problem: I can't use that $a anywhere, e.g. if I say:
echo $a
I would expect to see 0:3:19 ag
Kevin Mark wrote:
On Wed, Sep 27, 2006 at 09:22:05PM -0500, Ron Johnson wrote:
how about
b=`$a`
echo $b
or
echo $($a)
Bingo!!! Thanks!
Is that in the Advanced Bash-Scripting Guide?
H
echo `$a`
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
Atle Veka wrote:
In your example you are saying that $a is the function 'do_chrono', so
when you run $a, it runs the function and prints out the result. As
another poster indicated, you need to do it slightly differently:
# execute and store result in $a
a=$( do_chrono )
# print
echo $a
Yup
Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/06 18:51, Hugo Vanwoerkom wrote:
Hi,
On my way to elapsed time in a bash script, I created the do_chrono
command. It pumps the elapsed time to stdout.
So if I do:
a=do_chrono
and then:
$a
I get: 0:3:19.
Problem: I
On Wed, Sep 27, 2006 at 09:22:05PM -0500, Ron Johnson wrote:
>
> how about
> b=`$a`
> echo $b
or
echo $($a)
echo `$a`
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal | debian.home.pipeline.com |
| `. `' Operating System| go to coun
In your example you are saying that $a is the function 'do_chrono', so
when you run $a, it runs the function and prints out the result. As
another poster indicated, you need to do it slightly differently:
# execute and store result in $a
a=$( do_chrono )
# print
echo $a
Atle
-
Flying Crocodile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/06 18:51, Hugo Vanwoerkom wrote:
> Hi,
>
> On my way to elapsed time in a bash script, I created the do_chrono
> command. It pumps the elapsed time to stdout.
>
> So if I do:
>
> a=do_chrono
>
> and then:
>
> $a
>
> I get: 0:3:19.
>
> P
On 11/25/05, Metrics <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Can someone explain to me the following behaviour? I have this script
>
> #!/bin/sh
>
> LISTS=('debian-user' 'security-basics' 'hostap' 'pen-test' 'ntbugtraq'
> 'ion-general' 'vim' 'madwifi');
> LIST_COUNT=${#LISTS}
> echo $LIST_COUNT
>
On Mon, 2003-03-10 at 01:02, Jeff Elkins wrote:
> Jeff Elkins <[EMAIL PROTECTED]> writes:
> > ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e
> > s/arm.*/arm/ -e s/sa110/arm/
> >
> > I'm working on polishing my meagre shell scripting skills and would
> > appreciate some feedba
Jeff Elkins <[EMAIL PROTECTED]> writes:
> ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e
> s/arm.*/arm/ -e s/sa110/arm/
>
> I'm working on polishing my meagre shell scripting skills and would
> appreciate some feedback on the line above, quoted from the kernel
> Makefile.
Th
Hi Jeff,
Jeff Elkins <[EMAIL PROTECTED]> writes:
> ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e
> s/arm.*/arm/ -e s/sa110/arm/
>
> I'm working on polishing my meagre shell scripting skills and would
> appreciate some feedback on the line above, quoted from the ke
Jeff Elkins wrote:
> ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e
> s/arm.*/arm/ -e s/sa110/arm/
>
> I'm working on polishing my meagre shell scripting skills and would
> appreciate some feedback on the line above, quoted from the kernel Makefile.
Ew, that line seems to
David Z Maze wrote:
> Two somewhat common ways:
>
> uname -m | grep i.86 > /dev/null && echo x86
My I suggest using 'grep -q' to save the need to redirect?
> case `uname -m` in
> i?86) echo x86 ;;
> esac
I prefer the case statement approach.
Bob
pgp0.pgp
Description: PGP signat
Jeff Elkins <[EMAIL PROTECTED]> writes:
> ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e
> s/arm.*/arm/ -e s/sa110/arm/
>
> I'm working on polishing my meagre shell scripting skills and would
> appreciate some feedback on the line above, quoted from the kernel Makefile.
>
>
On Sun, Nov 03, 2002 at 12:28:26PM -0700, Bob Proulx wrote:
> get around 40,000 files in one single directory. Some filesystems
> such as JFS (and I think, not sure, XFS and ReiserFS too) store
> directies in B+ trees and are specifically designed to handle large
I know that ReiserFS does this. X
Neal Lippman <[EMAIL PROTECTED]> [2002-11-03 13:35:22 -0500]:
> Thanks. My "bug" here was using comma instead of space as the separator,
> and not realizing that the reason for x in {a,b,c,d...z} worked was
> because of the way the brace expansion was being done by the shell.
Ah, yes, csh style {o
On Sat, Nov 02, 2002 at 10:51:00PM -0500, Neal Lippman wrote:
>
> This works fine if I actually type out the entire alphabet list on the
> command line as above, but that's sort of a pain. So, I tried setting a
> shell variable to the alphabet string (export alpha="A,B,C,...,Z"), but
> then the co
Neal Lippman <[EMAIL PROTECTED]> [2002-11-02 22:51:00 -0500]:
> I am trying to solve a bash scripting problem, but I cannot figure it
> out.
>
> I frequently need to execute a command of the form:
> for x in {A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z); do
>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]> [2002-11-03 18:15:06 +0200]:
> On Sat, Nov 02, 2002 at 10:05:45PM -0600, Michael Heironimus wrote:
> > alpha="a b c d e z"
> > for x in $alpha ; do
> > echo $x
> > done
> >
> > I think this should work in any Bourne-style shell
>
> Doesn't wo
Matthias Hentges <[EMAIL PROTECTED]> [2002-11-03 18:32:29 +0100]:
> Am Son, 2002-11-03 um 04.51 schrieb Neal Lippman:
> > I frequently need to execute a command of the form:
> > for x in {A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z); do
> Your problem ist the wrong setting of th
Am Son, 2002-11-03 um 04.51 schrieb Neal Lippman:
> I am trying to solve a bash scripting problem, but I cannot figure it
> out.
>
> I frequently need to execute a command of the form:
> for x in {A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z); do
>;
> don
On Sat, Nov 02, 2002 at 10:05:45PM -0600, Michael Heironimus wrote:
> On Sat, Nov 02, 2002 at 10:51:00PM -0500, Neal Lippman wrote:
> > shell variable to the alphabet string (export alpha="A,B,C,...,Z"), but
> > then the command:
> > for x in {$alpha} ;
> > do
> > echo $x;
> >
On Sat, Nov 02, 2002 at 10:51:00PM -0500, Neal Lippman wrote:
> shell variable to the alphabet string (export alpha="A,B,C,...,Z"), but
> then the command:
> for x in {$alpha} ;
> do
> echo $x;
> done
> winds up printing the string "{A,B,C,...,Z}" rather than each l
Thank you all! Now it works.
* Gustavo Noronha Silva <[EMAIL PROTECTED]> [020320 09:25]:
...
> C="$A $B"
--
Karsten Heymann <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
CAU-University Kiel, Germany
Registered Linux User #221014 (http://counter.li.org)
On Tue, Mar 19, 2002 at 08:35:53PM +0100, Karsten Heymann wrote:
> Hi,
>
> I have once again come upon bash problem I can't solve. I'm writing a
> little bash frontend and one of the programs expects a option that includes
> spaces and is composed from two other shell var's. Example:
>
> #!/bin/b
Karsten Heymann, Tue, Mar 19, 2002 at 08:35:53PM +0100:
> Hi,
>
> I have once again come upon bash problem I can't solve. I'm writing a
> little bash frontend and one of the programs expects a option that includes
> spaces and is composed from two other shell var's. Example:
>
> #!/bin/bash
> A=
On Tue, 19 Mar 2002 20:35:53 +0100
Karsten Heymann <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have once again come upon bash problem I can't solve. I'm writing a
> little bash frontend and one of the programs expects a option that includes
> spaces and is composed from two other shell var's. Example:
Karsten Heymann <[EMAIL PROTECTED]> writes:
> Hi,
>
> I have once again come upon bash problem I can't solve. I'm writing
> a little bash frontend and one of the programs expects a option that
> includes spaces and is composed from two other shell var's. Example:
>
> #!/bin/bash
> A="Hello"
> B="
On Tue, 19 Mar 2002, Karsten Heymann wrote:
> Hi,
>
> I have once again come upon bash problem I can't solve. I'm writing a
> little bash frontend and one of the programs expects a option that includes
> spaces and is composed from two other shell var's. Example:
>
> #!/bin/bash
> A="Hello"
> B=
On Tue, Mar 19, 2002 at 20:35:53 +0100, Karsten Heymann wrote:
> A="Hello"
> B="Karsten"
> C=$A $B
> someprog --greeting $C
Variable expansion happens first:
someprog --greeting Hello Karsten
then tokenising, so someprog get three arguments:
1. --greeting
2. Hello
On Tue, Mar 19, 2002 at 08:35:53PM +0100, Karsten Heymann wrote:
> Hi,
>
> I have once again come upon bash problem I can't solve. I'm writing a
> little bash frontend and one of the programs expects a option that includes
> spaces and is composed from two other shell var's. Example:
>
> #!/bin/b
This should work, though I have not actually tried it:
#!/bin/bash
A="Hello"
B="Karsten"
C="$A $B"
someprog --greeting "$C"
pgpiX8Z2JqpWm.pgp
Description: PGP signature
D-Man writes:
> If he wants to start with bash he can. I think bash scripting is harder
> than python though.
Poor shell programming is quite easy. Good shell progamming is harder than
good Python programming.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
On Tue, Jan 30, 2001 at 10:55:53PM +0100, William Leese wrote:
[snip]
| > BTW, I don't use bash scripting for anything other than running
| > programs with some default options. I would prefer to use python for
| > this sort of thing, but it's up to you what you want to use.
|
| ..let the newbi
On Tue, Jan 30, 2001 at 09:40:53PM +0100, William Leese wrote:
> hi all
>
> i need a little help on a script. the following scripts function is to merge
> several parts of a html page together and insert a new piece of text from
> text.txt also it has to replace some words (the title, author, su
D-Man wrote:
>sed "s/Title/$TITLE/g" title.html >> file.txt &&
>
>Also, I'm not sure why you have double & at the end of the line. I
>think you want to run sed in the foreground, not the background. I
>don't understand what the second & does.
& by itself mean s to run in the backgr
> | > sed 's/Title/$TITLE/g' title.html >> file.txt &&
>
> ^^
> The single quotes are a problem too. Bash doesn't do any variable
> expansion in single quotes. ($TITLE will still be $TITLE for sed)
>
> Instead:
>
> sed "s/Title/$TITLE/g" title.html >> file.txt &&
>
> A
On 30-Jan-2001 William Leese wrote:
> hi all
>
> i need a little help on a script. the following scripts function is to merge
> several parts of a html page together and insert a new piece of text from
> text.txt also it has to replace some words (the title, author, submittor, and
> date) with
On Tue, Jan 30, 2001 at 10:02:38PM +0100, Matthias Wieser wrote:
| William Leese wrote:
|
| > sed 's/Title/$TITLE/g' title.html >> file.txt &&
^^
The single quotes are a problem too. Bash doesn't do any variable
expansion in single quotes. ($TITLE will still be $T
William Leese wrote:
> sed 's/Title/$TITLE/g' title.html >> file.txt &&
^
I think the g is missing, that is all I noticed
Ciao, mattHias
--
__ _ __ *
/\_/\ \ \_/ \_/ / * Matthias Wieser *
/ \ \ /
Hello,
If you read the man about bash, you will find out that all commands after a
pipeline are executed in a subshell.
It's not a bash bug !
Perhaps, if you try this :
#!/bin/bash -e
found_driver=0
echo -n "Starting sound driver: "
while read line; do
if /sbin/modprobe $line
"Carley, Jason (Australia)" wrote:
> >The kindest thing you can do for anyone in difficulty is to persuade him
> >that he really does need to study the manual.
>
> >He shouldn't even be posting questions until he has looked into the matter
> >himself and drawn a blank on all fronts. So any questi
On Mon, Jul 26, 1999 at 05:24:11PM +0930, Michael Talbot-Wilson wrote:
> > I love how people insist on firing off this remark. It is sooo
> > much more explanatory than pasting in a piece of the manpage then
> > breaking it down to a newbies' terms. Then _calmly_ telling them
> > (OFF THE LIST) th
Subject: RE: bash scripting
Date: Mon, Jul 26, 1999 at 06:03:35PM +1000
In reply to:Carley, Jason Australia"
Quoting Carley, Jason Australia"([EMAIL PROTECTED]):
>
> >The kindest thing you can do for anyone in difficulty is to persuade him
> >that he
>
> >The kindest thing you can do for anyone in difficulty is to persuade him
> >that he really does need to study the manual.
>
> >He shouldn't even be posting questions until he has looked into the matter
> >himself and drawn a blank on all fronts. So any question answered in the
> >manual de
>The kindest thing you can do for anyone in difficulty is to persuade him
>that he really does need to study the manual.
>He shouldn't even be posting questions until he has looked into the matter
>himself and drawn a blank on all fronts. So any question answered in the
>manual deserves either
> On Mon, Jul 26, 1999 at 08:18:48AM +0200, Gerhard Kroder wrote:
>
> > ever RTFM for bash? it says:
>
> I love how people insist on firing off this remark. It is sooo much more
> explanatory than pasting in a piece of the manpage then breaking it
> down to a newbies' terms. Then _calmly_
Gerhard Kroder wrote:
>
> Gerhard Kroder wrote:
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > Is there a way to put a 30 second pause in your bash script?
> >
> > ever RTFM for bash? it says:
> >
> >wait [n]
hey, shame on me, i know,... sorry,
my working day just starts and i'm not quit
On Mon, Jul 26, 1999 at 08:18:48AM +0200, Gerhard Kroder wrote:
> ever RTFM for bash? it says:
I love how people insist on firing off this remark. It is sooo much more
explanatory than pasting in a piece of the manpage then breaking it
down to a newbies' terms. Then _calmly_ telling them
>ever RTFM for bash? it says:
wait [n]
Wait for the specified process and return its ter
mination status. n may be a process ID or a job
specification; if a job spec is given, all pro
cesses in that job's pipeline are waited
On Mon, Jul 26, 1999 at 08:18:48AM +0200, Gerhard Kroder wrote:
> [EMAIL PROTECTED] wrote:
> >
> > Is there a way to put a 30 second pause in your bash script?
>
>
> ever RTFM for bash? it says:
>
>wait [n]
Erm, how exactly can you use this to wait for 30 seconds? I think he
wants some
Gerhard Kroder wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > Is there a way to put a 30 second pause in your bash script?
>
> ever RTFM for bash? it says:
>
>wait [n]
huups, guess it's me to RTFM...
of course you do not need (nor is it applicable) bash's builtin "wait" but
the commmand "
[EMAIL PROTECTED] wrote:
>
> Is there a way to put a 30 second pause in your bash script?
ever RTFM for bash? it says:
wait [n]
Wait for the specified process and return its ter
mination status. n may be a process ID or a job
specification;
[EMAIL PROTECTED] wrote:
>
> Is there a way to put a 30 second pause in your bash script?
>
sleep 30
You can also use s,m,h,d for seconds, minutes, hours and days
ie. sleep 1h
Bernhard
--
__ ___
// )___--"""-.
\ |,"( /`--"" `. Bernhar
On Sun, Jul 25, 1999 at 12:53:58AM -0500, [EMAIL PROTECTED] wrote:
> Is there a way to put a 30 second pause in your bash script?
Use:
sleep 30s
'man sleep' for more info. :-)
--
Matthew Gregan [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
On Sun, 25 Jul 1999 [EMAIL PROTECTED] wrote:
> Is there a way to put a 30 second pause in your bash script?
>
sleep 30
See man 1 sleep.
noah
PGP public key available at
http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html
or by 'finger -l [EMAIL PR
Eugene Sevinian <[EMAIL PROTECTED]> writes:
> Hi, ppl,
> I would like to know, is it possible to fork the standard stdout
> of some command into another two or three pipelines. The idea is to avoid
> unnecessary disk load during temporary file writing/reading. So I need
> something like this:
>
When Eugene Sevinian wrote, I replied:
>
> Hi, ppl,
> I would like to know, is it possible to fork the standard stdout
> of some command into another two or three pipelines.
Do a 'man tee' to check out the tee command. It may or may not
supply what you're looking for. You example below wasn't t
83 matches
Mail list logo
