[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] pid check when closing "bug"
yes, that is a problem, do you have a solution that still works when
someone tries to open a busy tty ?
> -----Original Message-----
> From: david LIBAULT [mailto:firstname.lastname@example.org]
> Sent: den 1 augusti 2001 11:13
> To: Mattias Ågren
> Cc: email@example.com
> Subject: Re: [bluetooth-dev] pid check when closing "bug"
> > > Remark on this last modification :
> > >
> > > Why should the pid be the same ? On my application, this test
> > > fails causing
> > > the kernel to crash when the tty is tried to be opened...
> > Not on mine ;) Can you describe in detail what goes wrong ?
> Yes, I can now.
> The ttyBTx port is opened by pppd (in my example, the pppd
> pid is 46). If
> your system has a /etc/ppp/ip-down script, this script is
> launched when the
> ppp connection terminates :
> Script /etc/ppp/ip-down started (pid 50)
> BT (driver) Unregistering tty on line 0
> BT (driver) bt_unregister_tty invalid pid.
> Current : 50 session : 46
> Script /etc/ppp/ip-down finished (pid 50)
> So in this case the ttyBTx port is opened with one pid and
> closed with
> another one, and my script doesn't open or close any port...
> > brgds
> > /Mattias
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org