From owner-freebsd-hackers Thu Oct 19 20:18:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id C8F6037B4CF for ; Thu, 19 Oct 2000 20:18:39 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id CA6D5A854; Fri, 20 Oct 2000 14:18:38 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id C6F43545D; Fri, 20 Oct 2000 13:18:38 +1000 (EST) Date: Fri, 20 Oct 2000 13:18:38 +1000 (EST) From: andrew@ugh.net.au To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: How to sense DCD on serial port? In-Reply-To: <58A002A02C5ED311812E0050044517F00D260A@erlangen01.atrada.de> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Oct 2000, Alexander Maret wrote: > DCD because this takes ernormous cpu time. Is there a possibility > to get a signal,intr or whatever, whenever the state of DCD changes? Umm....I'm not sure but wouldn't you get SIGHUP if DCD was dropped? It would look like the "dialed in user" had closed the connection. Not to sure though. I don't think you get anything when it goes high again although a blocked open will return so you might be able to hack up something there...but there must be a better way :-) > If not, what could you think of I have to do to implement such > a feature? You could look at the source for various serial port related stuff such as cu and tip. You may even get some hints from looking at getty etc that handles serial logins. Perhaps the sio source might help as well. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message