On 11/12/2015 3:56 AM, Bryan Drewery wrote:
I think it is fair to
say that most people don't understand how any of this works.
[...]
- No one really was trying to improve it head-on and focused on
FreeBSD's general audience needs.
The maintenance problems come down to expertise. Most develo
Ok, I had a hunch it was related to the use of jails.
I am just testing a patch that switches the nfsuserd over to
using an af_local socket, so this will be avoided.
(I think it makes more sense anyhow. I just never got around
to doing it.;-)
Thanks for the info, rick
- Original Message
FreeBSD_HEAD_i386 - Build #1858 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1858/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1858/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/1858/console
Change summaries:
292
On Thu, 10 Dec 2015, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem via email where the nfsuserd daemon sees
> requests coming from an IP# assigned to the machine instead of 127.0.0.1.
> Here's a snippet from his message:
> Ok, I have Plex in a jail and when I scan the remote NFS file
Firstly, nice writup - a few extra blank lines might have helped my eyes
though.
Bryan Drewery wrote:
> This mail is to outline my recent work, goals and motivations. This is
> long. This is not really a architectural review or discussion mail. I
...
> Some problems with the combined DIRDEPS_
This mail is to outline my recent work, goals and motivations. This is
long. This is not really a architectural review or discussion mail. I
am leaving those and details for their own threads where needed, so
please do not start discussions about any of the details here. We will
have them later
If you did that it would change the KPI a bit meaning lots
of thrashing in the code.
And on top of that you now would no longer return 0..
You would get 1 it was restarted or -1 it was not running but is now started.
Makes no sense to me sorry..
R
On Dec 10, 2015, at 7:35 AM, Hans Petter Selask
For callout_stop/drain you get
-1 == Callout as already gone off or is not running (usually the latter) else
the caller iks
not using locking properly or did not lock and check the active()
value (which would have returned not active so no stop
would have been needed);
0 == w
Hans:
Though it would not hurt to add your patch, its not possible
for callout_reset() to return anything but 1 or 0.
Only callout_stop(), callout_drain(), callout_async_drain() can return -1.
So I don’t think that this will fix it.
R
On Dec 4, 2015, at 11:34 AM, Hans Petter Selasky wrote:
>>
On 12/10/15 16:35, Randall Stewart wrote:
If you did that it would change the KPI a bit meaning lots
of thrashing in the code.
Hi,
There are only 5 consumers of the callout_reset() return code in the
FreeBSD 11-current kernel from what I can see:
grep -r "= callout_reset" sys/ | wc -l
On 12/10/15 16:25, Randall Stewart wrote:
For callout_stop/drain you get
-1 == Callout as already gone off or is not running (usually the latter) else
the caller iks
not using locking properly or did not lock and check the active()
value (which would have returned not active so no s
Hi,
Here is the backtrace for a reproducable panic seen with arptimer():
#0 doadump (textdump=0) at pcpu.h:221
#1 0x80385afb in db_dump (dummy=, dummy2=false,
dummy3=0, dummy4=0x0) at /usr/img/freebsd/sys/ddb/db_command.c:533
#2 0x803858ee in db_command (cmd_table=0x0) at
/
On Thu, Dec 10, 2015, at 07:37, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem via email where the nfsuserd daemon sees
> requests coming from an IP# assigned to the machine instead of 127.0.0.1.
> Here's a snippet from his message:
> Ok, I have Plex in a jail and when I scan the re
I think a local socket is probably the best solution long term. Using a
local socket also allows using filesystem permissions to control access
which is required for gssd but not necessarily for nfsuserd.
On 10 December 2015 at 13:37, Rick Macklem wrote:
> Hi,
>
> Mark has reported a problem vi
Hi,
Mark has reported a problem via email where the nfsuserd daemon sees
requests coming from an IP# assigned to the machine instead of 127.0.0.1.
Here's a snippet from his message:
Ok, I have Plex in a jail and when I scan the remote NFS file share the
*local* server's nfsuserd spams the logs
Ive literally just got this working on 10.2 after working on the code
posted on the review which you can find here:
https://reviews.freebsd.org/D4104
If you're happy running current then the patch file I linked in my comment
should apply cleanly and just work.
If you want 10.x then there's quite
Hi, I need to get one of my machines converted over from bios GPT zfsroot
boot to efi. I know you can boot freebsd under EFI with a ufs kernel but
this isnt the route i want. There are patches under test for EFI zfs root.
However when I read the thread it was unclear which version of these
patches
17 matches
Mail list logo
