From owner-freebsd-questions@FreeBSD.ORG Thu Jun 22 20:05:38 2006 Return-Path: X-Original-To: FreeBSD-Questions@freebsd.org Delivered-To: FreeBSD-Questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47EE316A4F4 for ; Thu, 22 Jun 2006 20:05:38 +0000 (UTC) (envelope-from af300wsm@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5CE744B8A for ; Thu, 22 Jun 2006 19:02:55 +0000 (GMT) (envelope-from af300wsm@gmail.com) Received: by nz-out-0102.google.com with SMTP id o1so551431nzf for ; Thu, 22 Jun 2006 12:02:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=LgZMfcHKl9+w5S3Be+pUTbuo8vo8DZwDPppGy46PaMu+Gw9vyiOyHlRUM9XPWp0Cw5A+Nwfj250vbp/YSpsXka+Y9qmQESZosBrZCh7sJFFjHnDGO6jSRKQynluKEbkx0/KBAQ2Fj58JPMxWru8SsMu5su1T0/z4A4bbIuiouf0= Received: by 10.37.22.68 with SMTP id z68mr2484139nzi; Thu, 22 Jun 2006 12:02:55 -0700 (PDT) Received: by 10.36.24.10 with HTTP; Thu, 22 Jun 2006 12:02:55 -0700 (PDT) Message-ID: <340a29540606221202r617b978aqecb2f68353f37b9@mail.gmail.com> Date: Thu, 22 Jun 2006 13:02:55 -0600 From: "Andrew Falanga" To: FreeBSD-Questions@freebsd.org In-Reply-To: <20060622185111.GA28343@Grumpy.DynDNS.org> MIME-Version: 1.0 References: <340a29540606220828i500905afq6d1ff81cf095cf88@mail.gmail.com> <6.0.0.22.2.20060622115945.02533de8@mail.computinginnovations.com> <340a29540606221119o16cab29ak5ae46156a3feca09@mail.gmail.com> <20060622185111.GA28343@Grumpy.DynDNS.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Serial programming on FreeBSD 6.0 RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2006 20:05:38 -0000 On 6/22/06, David Kelly wrote: > > On Thu, Jun 22, 2006 at 12:19:41PM -0600, Andrew Falanga wrote: > > Derek, > > > > No I didn't disable the getty on the port. To be honest, I didn't know > one > > was running. > > Its not going to be running by default. Even if it was then it would be > on /dev/ttyd1 not /dev/cuad1. What is supposed to happen is that getty > can listen for incoming on /dev/ttyd1 but if it doesn't have an active > connection it would be set aside while another comes along on the > call-out device to use the port. If ttyd1 is busy attempts to open cuad1 > should fail. > > > Second, the errors I'm receiving are: > > > > sio1: 2 more silo overflows (total 9) > > sio1: 280221 more tty-level buffer overflows (total 576898) > > Believe this is saying the data arrived and nobody picked it up. Yes, I'm sure of this as well. In fact, this is my problem. If I run the receive program that I build, it starts, apparrently configures the port as I want since the ctor doesn't throw the init error and just sits there until select times out waiting for data on the file descriptor opened in the same ctor. > One question I have is, why would kermit able to receive/send data > > across the port? I don't know if said this in my first message, but I > > started kermit on both the FreeBSD and Linux machines and was able to > > send/receive data in either direction. I didn't disable getty before > > doing that. > > /dev/cuad1 is rw for uucp:dialer and nothing for anyone else. What ID is > running your code? Generally one places users who are permitted to use > the serial ports into group dialer. Furthermore kermit needs the user's > uucp group permissions in order to create the UUCP lock in the hopes > that other programs will honor kermit's word that the device is busy. I did put my user in the dialer group. I'm not familiar with what you mean by the uucp group and the UUCP lock. Andy