I hope fixing these ports is easy and fast.
LOOK, let me be clear.
At the very last minute, the sysctl can be changed to return success
But if you guys aren't even going to try to cope with change, that's
coming off a little lame.
There are bad side effects from the past behaviour as well.
Je
Not ports related, but seeing these failures, it would also be worth
testing snmpd from base with hw.smt=0 on an HT machine.
On Thu, Sep 27 2018, Stuart Henderson wrote:
> On 2018/09/26 20:15, Stuart Henderson wrote:
>> On 2018/09/26 19:16, Stuart Henderson wrote:
>> > N.B. "Ports using KERN_CPTIME2 will need to be updated."
>> >
>> > This is likely to cause a bunch of breakage in things reporting CPU stats
>> > and ti
Stuart Henderson wrote:
> On 2018/09/26 20:15, Stuart Henderson wrote:
> > On 2018/09/26 19:16, Stuart Henderson wrote:
> > > N.B. "Ports using KERN_CPTIME2 will need to be updated."
> > >
> > > This is likely to cause a bunch of breakage in things reporting CPU stats
> > > and time is very short
Stuart Henderson wrote:
> On 2018/09/26 19:16, Stuart Henderson wrote:
> > N.B. "Ports using KERN_CPTIME2 will need to be updated."
> >
> > This is likely to cause a bunch of breakage in things reporting CPU stats
> > and time is very short to fix them before release.
> >
> > If you look after p
On Thu, Sep 27, 2018 at 09:25:51PM +0100, Stuart Henderson wrote:
> >
> > From a search over extracted ports source and cleaned up (ignoring ifdefs
> > etc):
>
> The rust-related things are not going to be actually using it so you
> can ignore those.
yes. it is the Rust libc (re)definition. so
On 2018/09/27 20:06, Stuart Henderson wrote:
> On 2018/09/26 20:15, Stuart Henderson wrote:
> > On 2018/09/26 19:16, Stuart Henderson wrote:
> > > N.B. "Ports using KERN_CPTIME2 will need to be updated."
> > >
> > > This is likely to cause a bunch of breakage in things reporting CPU stats
> > > an
On Thu, Sep 27, 2018 at 08:06:39PM +0100, Stuart Henderson wrote:
> On 2018/09/26 20:15, Stuart Henderson wrote:
> > On 2018/09/26 19:16, Stuart Henderson wrote:
> > > N.B. "Ports using KERN_CPTIME2 will need to be updated."
> > >
> > > This is likely to cause a bunch of breakage in things reporti
On 2018/09/26 20:15, Stuart Henderson wrote:
> On 2018/09/26 19:16, Stuart Henderson wrote:
> > N.B. "Ports using KERN_CPTIME2 will need to be updated."
> >
> > This is likely to cause a bunch of breakage in things reporting CPU stats
> > and time is very short to fix them before release.
> >
> >
On 2018/09/26 12:28, Chris Bennett wrote:
> I was about to file a bug report, perhaps this is relevant here?
>
> This was happening also on a recent snap before this one.
>
> Using spectrwm, my windows freeze up until I go yo another screen and
> back. For example, cat file or ls -la show screen
I was about to file a bug report, perhaps this is relevant here?
This was happening also on a recent snap before this one.
Using spectrwm, my windows freeze up until I go yo another screen and
back. For example, cat file or ls -la show screen output, but no
scrolling with mouse until I switch scre
On 2018/09/26 19:16, Stuart Henderson wrote:
> N.B. "Ports using KERN_CPTIME2 will need to be updated."
>
> This is likely to cause a bunch of breakage in things reporting CPU stats
> and time is very short to fix them before release.
>
> If you look after ports that do this, get onto a kernel wi
N.B. "Ports using KERN_CPTIME2 will need to be updated."
This is likely to cause a bunch of breakage in things reporting CPU stats
and time is very short to fix them before release.
If you look after ports that do this, get onto a kernel with this change
(very new commit so it probably won't be i
13 matches
Mail list logo
