From owner-freebsd-questions@FreeBSD.ORG  Thu Feb 14 19:01:51 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 34CF516A419
	for <freebsd-questions@freebsd.org>;
	Thu, 14 Feb 2008 19:01:51 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from m.it.okstate.edu (m.it.okstate.edu [139.78.2.129])
	by mx1.freebsd.org (Postfix) with ESMTP id 03FDF13C457
	for <freebsd-questions@freebsd.org>;
	Thu, 14 Feb 2008 19:01:50 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (localhost.it.okstate.edu [127.0.0.1])
	by m.it.okstate.edu (8.13.8/8.13.8) with ESMTP id m1EJ1oxh095809
	for <freebsd-questions@freebsd.org>;
	Thu, 14 Feb 2008 13:01:50 -0600 (CST)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <200802141901.m1EJ1oxh095809@m.it.okstate.edu>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <95807.1203015710.1@dc.cis.okstate.edu>
Date: Thu, 14 Feb 2008 13:01:50 -0600
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Re: FreeBSD6.2 What is the easiest Way to Capture RS-232 Serial
	Data? 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2008 19:01:51 -0000

Warren Block writes:
> Depending on the switch, you may find that the /usr/ports/comms utilities
> atslog or cdr_read will do the work for you.

Derek Ragona writes:
>You still need to handle when the cord is unplugged, or put the server in a 
>secure location away from other people.

>If you want the program to be more capable of staying running you can have 
>the program fork a child and if the child dies, fork a new child.  This is 
>the method used for many running services.  Just be sure if the child dies 
>the log file is closed and that same file is opened by the new child.

	Excellent ideas from both! Thank you.

Martin McCormick