From owner-freebsd-bluetooth@FreeBSD.ORG Wed Oct 19 23:05:28 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A9FB16A41F for ; Wed, 19 Oct 2005 23:05:28 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA2043D6A for ; Wed, 19 Oct 2005 23:05:27 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id j9JN5LJ17763; Wed, 19 Oct 2005 19:05:21 -0400 Message-ID: <4356D12F.7000006@savvis.net> Date: Wed, 19 Oct 2005 16:05:19 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Panagiotis Astithas References: <43519460.1090605@ebs.gr> <1129491219.1616.18.camel@localhost> <4353DBBC.2000508@savvis.net> <43541F79.6040008@ebs.gr> <43554BCE.7090309@savvis.net> <4355FD0C.2090702@ebs.gr> In-Reply-To: <4355FD0C.2090702@ebs.gr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: [RFC] rc.d integration for the bluetooth subsystem X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2005 23:05:28 -0000 Panagiotis, [...] >> that's fine. please give me some time for more careful review. also >> shouldn't rc.bluetooth be in /etc instead of /etc/rc.d? its >> similar to /etc/pccard_ether, is it not? > > If you pick rc.bluetooth, yes. On the other hand if you prefer the > rc.d version that I posted, it is more like, say /etc/rc.d/netif, so > it should be in /etc/rc.d. If you are concerned about having a script > in rc.d that is not executed at boot time, there is also the > precedent of /etc/rc.d/dhclient and the other scripts with the > nostart keyword. > > It is also my impression that rc.foo scripts in /etc are being > deprecated these days, but I might be wrong. We could ask freebsd-rc > for a clarification. yes. basically i'm not sure where your version of bluetooth rc.d script should go /etc or /etc/rc.d the other questions i have is 1) was there any particular reason to put "shutdown" word into "KEYWORD:"? the way i understand it: your bluetooth script will be called with "stop" command on system shutdown, however there will be no device name, so ${dev} will be unset. am i correct here? 2) what is the reason for calling "/etc/rc.d/{hcsecd,sdpd} {start,stop}" from "bluetooth_start()/bluetooth_stop()"? shouldn't these be controlled by their own xxx_enable variables? for example you do not need sdpd(8) running unless you want to provide services to the remote clients. also both sdpd(8) and hcsecd(8) bind to "any" bd_addr, so there is no reason to restart them even if particular device comes and goes. what is important here is to kill daemons (providing services, such as rfcomm_pppd(8)) if they were bound (i.e. listening) to the device that went away. however this is a corner case. usually service daemons listen on "any" address and thus there is no need to restart them. thanks, max