Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site ittvax.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!ittvax!long
From: long@ittvax.UUCP (H. Morrow Long [Systems Center])
Newsgroups: net.unix,net.bugs
Subject: Re: more on echo command
Message-ID: <1651@ittvax.UUCP>
Date: Mon, 15-Apr-85 19:30:34 EST
Article-I.D.: ittvax.1651
Posted: Mon Apr 15 19:30:34 1985
Date-Received: Sat, 20-Apr-85 01:04:44 EST
References: <199@phri.UUCP> <1194@houxm.UUCP>
Organization: ITT-ATC, Stratford Ct.
Lines: 32
Xref: linus net.unix:3619 net.bugs:552

> While on the topic of "echo", it is remarkably hard to have a background
> process output just a bell character with no carriage return (to signal
> that it is done, say, while I am in a vi session).  I had been using a
> 'C' routine for this purpose, and finally discovered that I could say:
> 	echo "^G\c"
> only to find out it does not work with UCB 4.2.

	For a good time read the story of echo in Kernighan and Pike's
	the Unix Programming Environment.  The following program will
	work under 4.2bsd.

#! /bin/sh
#
#	Ring bell continuously, frequency varies with load average.
#	To be really irritating to other users redirect the output 
#	to their terminals, i.e. 'annoy > /dev/ttyi4 &'.
#
while true
do
	echo -n "" 
done
-- 

				H. Morrow Long
				ITT-ATC Systems Center,
				1 Research Drive Shelton, CT  06484
				Phone #: (203)-929-7341 x. 634
	
path = {allegra bunker ctcgrafx dcdvaxb dcdwest ucbvax!decvax duke eosp1
	ittral lbl-csam milford mit-eddie psuvax1 purdue qubix qumix 
	research sii supai tmmnet twg uf-cgrl wxlvax yale}!ittvax!long