On 8/22/2019 6:51 PM, John Baldwin wrote:
> On 8/21/19 5:47 PM,
> # dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] =
> count() }'
> dtrace: description 'fbt::_gone_in:entry ' matched 1 probe
>
> However, It doesnt show anything after that even as I get the
> deprecation
On 8/21/19 5:47 PM, Mike Tancsa wrote:
> On 8/21/2019 6:38 PM, John Baldwin wrote:
>> On 8/21/19 9:08 AM, mike tancsa wrote:
>>> On 8/21/2019 12:00 PM, John Baldwin wrote:
dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] =
count()'
>>> Thanks, I am not familiar with
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2019-08-18
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2019-08-12 to 2019-08-18.
During this period, we have:
* 2205
On 2019-08-22 12:43, Miroslav Lachman wrote:
>> I run in to something similar from time to time from about 10.x or 8.x (i
>> skipped 9.x)
>> I do not remember exactly what command did the corruption, if it was vipw or
>> chsh or something else to manipulate user database. The fix was easy - run
Miroslav Lachman wrote on 2019/08/22 11:21:
Alan Somers wrote on 2019/08/22 04:07:
Unless, of course your master.passwd file was damaged. But the *.db
files are really just caches for faster access to user data. The
real master file is master.passwd.
The ch* tools typically just change
Alan Somers wrote on 2019/08/22 04:07:
On Wed, Aug 21, 2019 at 7:22 PM Tom Samplonius wrote:
On Aug 21, 2019, at 2:55 PM, Alan Somers wrote:
Today I tried to use chsh to change my shell from bash to fish. The
command completed successfully, but new logins continued to use bash!
