On Sat, Sep 8, 2012 at 12:29 PM, Alexander Motin wrote:
> Hi.
>
> It seems like both of your problems have the same cause: device report wrong
> size of INQUIRY data, that causes failure on attempt to fetch it. With
> FreeBSD 9.0 it caused domain validation failures and so reduced transfer
> rate,
On 09.09.2012 16:25, kirk russell wrote:
On Sat, Sep 8, 2012 at 12:29 PM, Alexander Motin wrote:
Hi.
It seems like both of your problems have the same cause: device report wrong
size of INQUIRY data, that causes failure on attempt to fetch it. With
FreeBSD 9.0 it caused domain validation failu
On Sun, Sep 9, 2012 at 4:54 PM, Alexander Motin wrote:
> On 09.09.2012 16:25, kirk russell wrote:
>>
>> On Sat, Sep 8, 2012 at 12:29 PM, Alexander Motin wrote:
>>>
>>> Hi.
>>>
>>> It seems like both of your problems have the same cause: device report
>>> wrong
>>> size of INQUIRY data, that cause
On Thu, 30 Aug 2012, Norbert Aschendorff wrote:
Hi,
I tested it using tcpdump: http://nopaste.info/9394068f54_nl.html
The length field says for each packet 1408 bytes, so that should be OK.
The Wireshark instance on the iperf server says something like "16732
bytes on wire" for the most packet
I am running bsnmpd with basic snmpd.config (only community and location
changed).
When there is a problem with HDD and disk disapeared from ATA channel
(eg.: disc physically removed) the bsnmpd always dumps core:
kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped)
I see this
On Sun, Sep 09, 2012 at 11:56:55PM +0200, Miroslav Lachman wrote:
> I am running bsnmpd with basic snmpd.config (only community and location
> changed).
>
> When there is a problem with HDD and disk disapeared from ATA channel
> (eg.: disc physically removed) the bsnmpd always dumps core:
>
> k
