On 04/26, Shawn Debnath wrote:
> Synced to r298678 this evening and after a reboot, powerd fails to start
> with the following error in messages:
>
> Apr 26 17:54:12 titan root: /etc/rc: WARNING: failed to start powerd
>
> Manually trying to start it via service throws:
>
> $ sudo service po
On Wed, Apr 27, 2016 at 11:32:05AM +0800, Julian Elischer wrote:
> the following change is sitting out at github, to add kqueue support
> for more file operations:
>
> https://github.com/dmatveev/libinotify-kqueue/blob/master/patches
>
> does anyone have reasons why we shouldn't import this cha
One (two?) question(s).
Any mechanism for monitoring file alternation (modify/create/rename/...)
should NOT avoid unmounting filesystem.
With this aspect, are these patches conforming?
If not, there should be some mechanisms to stop monitoring per device /
share basis. Are there some?
*Imagine
On Wed, Apr 27, 2016 at 11:32:05AM +0800, Julian Elischer wrote:
> the following change is sitting out at github, to add kqueue support
> for more file operations:
>
> https://github.com/dmatveev/libinotify-kqueue/blob/master/patches
>
> does anyone have reasons why we shouldn't import this chan
On Wed, Apr 20, 2016 at 08:16:36AM -0500, Andrew Berg wrote:
> Also, how much response do you expect in ~17 hours? Developers need time to
> sleep, do their day jobs, and formulate a detailed response to a detailed
> email.
OK, week later -- no any ("interesting", "not interesting", "know
issus
24.04.16 20:46, Larry Rosenman пишет:
> On 2016-04-21 20:56, Johannes Dieterich wrote:
>> On Thu, Apr 21, 2016 at 12:16 PM, Allan Jude
>> wrote:
>>> On 2016-04-21 10:46, Johannes Dieterich wrote:
Dear all,
with r298385, I observe extremely long times from turning on my laptop
t
On April 27, 2016 2:50:13 PM GMT+02:00, Boris Samorodov wrote:
>24.04.16 20:46, Larry Rosenman пишет:
>> On 2016-04-21 20:56, Johannes Dieterich wrote:
>>> On Thu, Apr 21, 2016 at 12:16 PM, Allan Jude
>>> wrote:
On 2016-04-21 10:46, Johannes Dieterich wrote:
> Dear all,
>
> with
Hi All,
There is no smtp service after recent update:
-
% sockstat -4l
USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
ADDRESS
root sshd 879 4 tcp4 *:22 *:*
root syslogd663 7 udp4 *:514 *:*
-
I use (almost) def
On Wed, Apr 27, 2016 at 04:34:29PM +0300, Boris Samorodov wrote:
> Hi All,
>
> There is no smtp service after recent update:
> -
> % sockstat -4l
> USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
> ADDRESS
> root sshd 879 4 tcp4 *:22 *:*
> root
27.04.16 17:08, Chagin Dmitry пишет:
> On Wed, Apr 27, 2016 at 04:34:29PM +0300, Boris Samorodov wrote:
>> Hi All,
>>
>> There is no smtp service after recent update:
>> -
>> % sockstat -4l
>> USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
>> ADDRESS
>> root sshd 87
27.04.16 16:30, Allan Jude пишет:
> On April 27, 2016 2:50:13 PM GMT+02:00, Boris Samorodov
> wrote:
>> 24.04.16 20:46, Larry Rosenman пишет:
>>> On 2016-04-21 20:56, Johannes Dieterich wrote:
On Thu, Apr 21, 2016 at 12:16 PM, Allan Jude
wrote:
> On 2016-04-21 10:46, Johannes Diete
On Monday, April 25, 2016 07:27:00 PM Shawn Webb wrote:
> Here's the backtrace:
>
> lock order reversal: (sleepable after non-sleepable)
> 1st 0xf8002a914840 vm object (vm object) @ /usr/src/sys/vm/vm_fault.c:361
> 2nd 0x822bf9c8 (&nm_mem)->nm_mtx ((&nm_mem)->nm_mtx) @
> /usr/src/sy
On Wed, Apr 27, 2016 at 05:08:47PM +0300, Chagin Dmitry wrote:
> On Wed, Apr 27, 2016 at 04:34:29PM +0300, Boris Samorodov wrote:
> > Hi All,
> >
> > There is no smtp service after recent update:
> > -
> > % sockstat -4l
> > USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
> >
FreeBSD_HEAD_i386 - Build #2979 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2979/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2979/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2979/console
Change summaries:
2
On (19/04/2016 13:36), Adrian Chadd wrote:
> It's cool. I have positive and negative reactions, and I'm totally
> happy to let people try it out at a larger scale and learn from
> mistakes.
>
> Because, honestly - fuck it, we've been behind for too long. We need
> more mature tools and knowledge w
Hello
Currently _POSIX2_VERSION is set to 199212L [1]:
$ grep _POSIX2_VERSION /usr/src/include/*.h
/usr/src/include/unistd.h:#define _POSIX2_VERSION 199212L
Unfortunately, I couldn't find any authoritative open source for
possible _POSIX2_VERSION values. But, for example, GNU diff u
FreeBSD_HEAD_i386 - Build #2980 - Still Failing:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2980/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2980/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2980/console
Change summari
FreeBSD_HEAD_i386 - Build #2981 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2981/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2981/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2981/console
Change summaries:
298
I am running into this on amd64 as well.
On 4/27/16, 11:14 AM, "owner-freebsd-curr...@freebsd.org on behalf of
jenkins-ad...@freebsd.org" wrote:
>FreeBSD_HEAD_i386 - Build #2979 - Failure:
>
>Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2979/
>Full change log: https:/
19 matches
Mail list logo