From owner-freebsd-questions Mon Jan 21 21: 4:44 2002 Delivered-To: freebsd-questions@freebsd.org Received: from transbay.net (www.transbay.net [209.133.53.217]) by hub.freebsd.org (Postfix) with ESMTP id 9766837B416 for ; Mon, 21 Jan 2002 21:04:40 -0800 (PST) Received: from transbay.net (rigel.transbay.net [209.133.53.177]) by transbay.net (8.11.2/8.11.2) with ESMTP id g0M54ch63808; Mon, 21 Jan 2002 21:04:38 -0800 (PST) Message-ID: <3C4CF496.43333D21@transbay.net> Date: Mon, 21 Jan 2002 21:11:50 -0800 From: UCTC Sysadmin Organization: UC Telecommunications Company X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mmercer@nc.rr.com, freebsd-questions@freebsd.org Subject: Re: machine beeps periodically. References: <3C460679.5D3BCF7F@nc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Verify the BIOS thing to be safe. Something is asking for the beep. If your machine is online 24x7 and people know you, it could be someone trying to "talk" to you - the beep would correspond to one window where "Talk requested" message is displayed. Esp if it happens at completely random times, and the beep occurs a couple times before it gives up. I don't know if it's meaningful but you could try changing permissions for the speaker device to stop access and then look through logs for a process that complains that it can't access the speaker. Check (comsat/biff etc.) that a mail notification thing is not accidentally configured to run. It won't necessarily beep when you get mail, it may only beep if there is new mail after the polling period (every N minutes.) Assuming the beep is not in reply to your keystrokes ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message