On Tue, Mar 21, 2017 at 10:54 PM, Jamie Landeg-Jones
> I realise there are advantages of GNUgrep and also advantages of BSDgrep,
> hence why they are currently both available (and thanks for your work on
> getting bsd grep up to parity) but I don't understand why on the default
> install,
> xzgrep
Kyle Evans wrote:
> >
> > Am I really the first to notice, or am I missing something here?
>
> Yes, but only slightly. =) If you do `grep -V`, you should find that
> your system is actually using GNU grep. Please refer to:
> https://svnweb.freebsd.org/base/head/gnu/usr.bin/grep/ -- this one
> doe
On Tue, Mar 21, 2017 at 9:33 PM, Jamie Landeg-Jones
wrote:
> I've just noticed that the hard links for xzgrep / xzegrep / xzfgrep / lzgrep
> / lzgrep / lzfgrep
> are missing from my source-built FreeBSD 11 release.
Confirmed, but there's good reason -- see next section.
> I've tracked it down t
I've just noticed that the hard links for xzgrep / xzegrep / xzfgrep / lzgrep /
lzgrep / lzfgrep
are missing from my source-built FreeBSD 11 release.
I've tracked it down to a commit almost 2 years ago..
https://svnweb.freebsd.org/base/head/usr.bin/grep/Makefile?r1=277939&r2=284345&pathrev=31568
On 2017-Mar-18, at 9:10 PM, Mark Millard wrote:
>
> On 2017-Mar-18, at 5:53 PM, Mark Millard wrote:
>
>> A new, significant discovery follows. . .
>>
>> While checking out use of procstat -v I ran
>> into the following common property for the 3
>> programs that I looked at:
>>
>> A) My small
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #19 from Scott Larson ---
(In reply to Cassiano Peixoto from comment #15)
Tossing in that I've been seeing this panic on stock kernel 11.0-p8 machines
running on Atom C2750s. The failure shown by kgdb output looks identical to
I am see lock contetntion cuased by aio read (same file segment from
multiple process simultaneous):
07.74% [26756]lock_delay @ /boot/kernel/kernel
92.21% [24671] __mtx_lock_sleep
52.14% [12864] vm_page_enqueue
100.0% [12864] vm_fault_hold
87.71% [11283]vm
