From: "Rob Taft" <rtaft@sensis.com>
To: <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] DHCPD and Bluetooth
Date: Wed, 12 May 2004 17:27:24 -0400 [thread overview]
Message-ID: <00e401c43867$ee3193f0$80c8fea9@Perigee.Perigeellc.com> (raw)
In-Reply-To: 200405122257.01637.pavouk@pavouk.org
I think I'm almost there.
I noticed that it is not HW based after I posted. I saw in
/var/log/messages a message that occurred ever connection:
May 12 17:01:20 SMED /etc/hotplug/net.agent: invoke ifup bnep0
So I went into the net.agent file and found this line that matched the
output:
debug_mesg invoke ifup $INTERFACE
I added more lines to that so now it looks like this:
if [ -x /sbin/ifup ]; then
debug_mesg invoke ifup $INTERFACE
debug_mesg LALALALALALALALALALA #ADDED THIS
exec /sbin/ifup $INTERFACE
debug_message Attempting to restart dhcpd. #ADDED THIS
exec /etc/init.d/dhcpd restart #ADDED THIS
else
mesg "how do I bring interfaces up on this distro?"
fi
I then restarted my entire system....and the 2nd 2 lines were never reached.
I added the LALALA line after and that appears in the logs...so I'm guessing
that "exec /sbin/ifup $INTERFACE" is causing the script to exit
----- Original Message -----
From: "Pavel Ruzicka" <pavouk@pavouk.org>
To: <bluez-users@lists.sourceforge.net>
Cc: "Rob Taft" <rtaft@sensis.com>
Sent: Wednesday, May 12, 2004 4:57 PM
Subject: Re: [Bluez-users] DHCPD and Bluetooth
> Hello,
>
> > restart it. I don't think hotplug is what I am looking for since it is
> > hardware connection based.
>
> This is not only hardware connection based. When you try setup network
from
> remote device, that kernel call /sbin/hotplug with NET action.
> You can edit script "/etc/hotplug.d/default/default.hotplug" or other in
your
> distribution and uncomment line "DEBUG=yes export DEBUG".
> Later you can look in to log file for interesting messages ;-)
> In this case will be probably interesting script /etc/hotplug/net.agent.
>
> Best regards,
>
> Pavel Ruzicka
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver
> higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-12 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 16:07 [Bluez-users] DHCPD and Bluetooth Rob Taft
2004-05-12 16:44 ` Mykel
2004-05-12 17:55 ` Rob Taft
2004-05-12 19:03 ` Michal Semler
2004-05-12 20:23 ` Rob Taft
2004-05-12 20:57 ` Pavel Ruzicka
2004-05-12 21:27 ` Rob Taft [this message]
2004-05-12 21:47 ` Achim Bohnet
2004-05-13 12:24 ` Rob Taft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00e401c43867$ee3193f0$80c8fea9@Perigee.Perigeellc.com' \
--to=rtaft@sensis.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox