> On Jul 21, 2019, at 4:17 PM, Andriy Gapon wrote:
>
>> On 20/07/2019 20:08, Patrick Kelsey wrote:
>>
>>
>> On Fri, Jul 19, 2019 at 10:07 AM Andriy Gapon > <mailto:a...@freebsd.org>> wrote:
>>
>>
>>Recently we experienced a
On Fri, Jul 19, 2019 at 10:07 AM Andriy Gapon wrote:
>
> Recently we experienced a strange problem.
> We noticed a lot of these messages in the logs:
> vmx0: watchdog timeout on queue 2
> (always queue 2)
> Also, we noticed that connections to some end points did not work at all
> while others wo
On Mon, Feb 12, 2018 at 12:04 PM, John Baldwin wrote:
> On Saturday, February 10, 2018 01:46:33 PM Garrett Wollman wrote:
> > In article
> > ,
> > asom...@freebsd.org writes:
> >
> > >On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen
> > >wrote:
> >
> > >> Is there any expectation that this
On Fri, Mar 17, 2017 at 1:31 PM, O. Hartmann wrote:
> Am Fri, 17 Mar 2017 20:07:35 +0300
> Slawa Olhovchenkov schrieb:
>
> > On Fri, Mar 17, 2017 at 05:53:24PM +0100, O. Hartmann wrote:
> >
> > > Am Fri, 17 Mar 2017 15:04:29 +0300
> > > Slawa Olhovchenkov schrieb:
> > >
> > > > On Fri, Mar 17,
On Sun, Aug 9, 2015 at 6:36 AM, Gleb Smirnoff wrote:
> On Sun, Aug 09, 2015 at 12:28:22PM +0200, Kristof Provost wrote:
> K> Hi,
> K>
> K> I’ve run into a reproducible panic on a VIMAGE kernel with ‘sysctl -a’.
> K>
> K> Relevant backtrace bits:
> K> #8 0x80e7dd28 in trap (frame=0xfe
On Sat, May 2, 2015 at 10:25 PM, Adrian Chadd wrote:
> hi,
>
> Hm, should we be upping this limit automatically? Can we get cpu
> counts or memory amount early enough in boot to have a hope of
> auto-tuning?
>
> 64 seems low, 1024 seems high as a default. :)
>
What is it that's exhausting the b
On Wed, Sep 10, 2014 at 3:00 AM, Andrey Chernov wrote:
> On 09.09.2014 21:53, Patrick Kelsey wrote:
> > I don't think it is worth the trouble, as given the larger pattern of
> > libc routines requiring multiple capsicum rights, it seems one will in
> > general have t
On Mon, Sep 8, 2014 at 6:00 PM, Andrey Chernov wrote:
> On 09.09.2014 1:13, Patrick Kelsey wrote:
> > You make a godo point about the wider use of fcntl() in libc - aside
> > from the rpc code, by my count there are 14 other entry points in libc
> > that use fcntl in thei
On Mon, Sep 8, 2014 at 4:42 PM, Andrey Chernov wrote:
> On 09.09.2014 0:28, Patrick Kelsey wrote:
> > In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
> > non-append, write-only path. Consequently, programs that use _ftello()
> > (via ftell, fgetpos, f
In r268997, _ftello() was modified to use _fcntl(F_GETFL) in the
non-append, write-only path. Consequently, programs that use _ftello()
(via ftell, fgetpos, fsetpos, fseek, rewind...) on non-append, write-only
files and that use capsicum to restrict capabilities on the associated fds
to [CAP_SEEK,
10 matches
Mail list logo
