Hi,
I am currently working on converting syslogd to libevent. Theo
recommended to do that before adding tcp and tls support.
With this diff all my regression tests for syslogd pass. I will
try to pull parts of the diff into separate changes to make review
easier. I have not tested the syslogc
Hi,
When writing my regression test for syslogd, I realized that with
LOG_CONS and LOG_PERROR trailing new lines are printed. Of course
Perl Sys::Syslog that I use for the tests has bugs and appends '\n'
in cases where it should not.
But then I found this sentence in our man 3 syslog:
A tra
On Fri, 29 Aug 2014, Mike Belopuhov wrote:
> On 29 August 2014 11:26, Stefan Fritsch wrote:
> > On Fri, 29 Aug 2014, Miod Vallat wrote:
> >> > sc->sc_xfer_max is computed according to the host's capabilities. What I
> >> > want to simulate with this diff is a host adapter that can only cope with
On Fri, 29 Aug 2014, Daniel Jakots wrote:
> Hi,
>
> When running tcpbench -su, a lot of them are counted as "missed PCB
> cache".
...
> + n = recvfrom(fd, ptb->dummybuf, ptb->dummybuf_len, 0,
> + (struct sockaddr *)&ss, &slen);
> + if (n > 0 && connect(fd,
Hi,
When running tcpbench -su, a lot of them are counted as "missed PCB
cache".
I reboot the computer then netstat -sp udp gives
udp:
10 datagrams received
0 with incomplete header
0 with bad data length field
0 with bad checksum
0 with no checksum
On Fri, Aug 29, 2014 at 01:48:15PM +0200, Mike Belopuhov wrote:
> On 29 August 2014 13:44, Jason McIntyre wrote:
> > On Fri, Aug 29, 2014 at 01:39:57PM +0200, Mike Belopuhov wrote:
> >> On 29 August 2014 08:19, Jason McIntyre wrote:
> >> >
> >> > is this correct? i'm not a user myself, but the te
On 29 August 2014 13:44, Jason McIntyre wrote:
> On Fri, Aug 29, 2014 at 01:39:57PM +0200, Mike Belopuhov wrote:
>> On 29 August 2014 08:19, Jason McIntyre wrote:
>> >
>> > is this correct? i'm not a user myself, but the text states that
>> > "special", for mount_mfs, is "typically that of the pr
On Fri, Aug 29, 2014 at 01:39:57PM +0200, Mike Belopuhov wrote:
> On 29 August 2014 08:19, Jason McIntyre wrote:
> >
> > is this correct? i'm not a user myself, but the text states that
> > "special", for mount_mfs, is "typically that of the primary swap area".
> > how would you even define the sw
On 29 August 2014 08:19, Jason McIntyre wrote:
>
> is this correct? i'm not a user myself, but the text states that
> "special", for mount_mfs, is "typically that of the primary swap area".
> how would you even define the swap area without a disklabel?
>
> jmc
>
sort of yes. mount_mfs(8) says th
On 29 August 2014 11:26, Stefan Fritsch wrote:
> On Fri, 29 Aug 2014, Miod Vallat wrote:
>> > sc->sc_xfer_max is computed according to the host's capabilities. What I
>> > want to simulate with this diff is a host adapter that can only cope with
>> > transfers < 64k == MAXPHYS.
>>
>> Back to your
On Fri, 29 Aug 2014, Miod Vallat wrote:
> > sc->sc_xfer_max is computed according to the host's capabilities. What I
> > want to simulate with this diff is a host adapter that can only cope with
> > transfers < 64k == MAXPHYS.
>
> Back to your original problem, you might want to print the sc_lin
> > > +#define MINPHYS (20*1024)
> >
> > This makes no sense. If you want to override MINPHYS, you need to
> > override for the whole kernel, not only here.
>
> MINPHYS is just a name I have chosen. It is not used anywhere else in the
> kernel. You are confusing this with MAXPHYS.
Oops
On Fri, 29 Aug 2014, Miod Vallat wrote:
> > +++ b/sys/dev/pci/vioblk.c
> > @@ -63,6 +63,7 @@
> > #include
> > #include
> >
> > +#define MINPHYS(20*1024)
>
> This makes no sense. If you want to override MINPHYS, you need to
> override for the whole kernel, not only here.
MINPHYS
> +++ b/sys/dev/pci/vioblk.c
> @@ -63,6 +63,7 @@
> #include
> #include
>
> +#define MINPHYS (20*1024)
This makes no sense. If you want to override MINPHYS, you need to
override for the whole kernel, not only here.
> @@ -157,6 +158,8 @@ vioblk_minphys(struct buf *bp, struct scsi
No, also happens on ffs. If the root FS is on an affected device, it looks
like this:
root on sd0a (9e7002f8647a2403.a) swap on sd0b dump on sd0b
clock: unknown CMOS layout
panic: kernel diagnostic assertion "xs->datalen <= MINPHYS" failed: file
"../../../../dev/pci/vioblk.c", line 405
Stopped
15 matches
Mail list logo
