From owner-freebsd-questions Sat Jun 30 12: 2:33 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 9CA5A37B403 for ; Sat, 30 Jun 2001 12:02:29 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.3/8.11.3) id f5UJ2Qo19582; Sat, 30 Jun 2001 14:02:26 -0500 (CDT) (envelope-from dan) Date: Sat, 30 Jun 2001 14:02:26 -0500 From: Dan Nelson To: parv Cc: f-q Subject: Re: why does the bell ring twice? Message-ID: <20010630140226.A3334@dan.emsphone.com> References: <20010630134554.A5930@moo.holy.cow> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20010630134554.A5930@moo.holy.cow> User-Agent: Mutt/1.3.19i X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Jun 30), parv said: > can anybody enlighten me why do bash & ksh ring the bell twice > instead of once? >=20 > # echo =07 & >=20 > second beep is produced when you press enter when new/clear shell > prompt shows up. Because when you background a job, the shell keeps track of it and notifies you when the command completes. Try running "echo test &", and look at the "done" message. That's where your second bepp is coming from. --=20 Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message