On Tuesday, January 04, 2011 09:08:24 Eugene Grosbein wrote:
> > There is race in devd and our rc-subsystem if wpa_supplicant is involved
> > effectivly resulting in starting wpa_supplicant twice. Both instances try
> > to take over the wlan device which results in what you are seeing.
> > I have n
On 04.01.2011 15:06, Bernhard Schmidt wrote:
>> Perhaps, wrapping wpa_supplicant invocation into "lockf -t0" would help
>> to eliminate race?
>
> Possibly, but I don't think this is the way to go.
>
> Currently wpa_supplicant has this code:
> /*
> * Mark the interface as down to
On Tuesday, January 04, 2011 10:09:15 Eugene Grosbein wrote:
> On 04.01.2011 15:06, Bernhard Schmidt wrote:
> >> Perhaps, wrapping wpa_supplicant invocation into "lockf -t0" would help
> >> to eliminate race?
> >
> > Possibly, but I don't think this is the way to go.
> >
> > Currently wpa_supplic
On 04.01.2011 15:39, Bernhard Schmidt wrote:
>> Proper fine-grained locking was always good solution for race problem :-)
>> How about using flock(2) in wpa_supplicant source code?
>
> I don't see any flock'able resource shared between instances, do you?
Just use pidfile(3) :-)
I would like to know where I can find the source code for the TCP
implementation so I can do some hacking on it.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-u
*bump*
On 10/29/10 02:17, Aragon Gouveia wrote:
http://www.freebsd.org/cgi/query-pr.cgi?pr=151400
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...
On 01/04/2011 04:46, Mickey Harvey wrote:
> I would like to know where I can find the source code for the TCP
> implementation so I can do some hacking on it.
Have you looked through the repository at all ?
http://svn.freebsd.org/
--
Regards,
jhell,v
JJH48-ARIN
_
I get them as well... on my em devices. I was just thinking of
upgrading to a dual port igb I have kicking around, but your email is
not encouraging. :)
# grep watchdog /var/log/message
Jan 2 21:13:38 turtle kernel: em5: watchdog timeout -- resetting
Jan 3 04:31:37 turtle kernel: em4: watch