On 03/23/2018 09:58 AM, William Allen Simpson wrote:
On 3/23/18 7:59 AM, Daniel Gryniewicz wrote:
Thanks, Tomk. PR is here: https://review.gerrithub.io/404945
Actually, it seems fairly elegant.
ntirpc and rdma also have the USE_ and _USE_ convention. Both
require libraries, and would benef
On 3/23/18 7:59 AM, Daniel Gryniewicz wrote:
Thanks, Tomk. PR is here: https://review.gerrithub.io/404945
Actually, it seems fairly elegant.
ntirpc and rdma also have the USE_ and _USE_ convention. Both
require libraries, and would benefit from defaults with
enforcement checking for the cma
Thanks, Tomk. PR is here: https://review.gerrithub.io/404945
Daniel
On 03/22/2018 05:39 PM, TomK wrote:
On 3/22/2018 12:50 PM, Daniel Gryniewicz wrote:
A side note, happy to test for you guy's once you have this done.
No, we can't. I'm working on a set of macros that make this work (as
far
On 3/22/2018 12:50 PM, Daniel Gryniewicz wrote:
A side note, happy to test for you guy's once you have this done.
No, we can't. I'm working on a set of macros that make this work (as
far as I can tell) and aren't *too* ugly. Hopefully, this will work out.
Daniel
On 03/22/2018 12:13 PM, Mala
No, we can't. I'm working on a set of macros that make this work (as
far as I can tell) and aren't *too* ugly. Hopefully, this will work out.
Daniel
On 03/22/2018 12:13 PM, Malahal Naineni wrote:
That could be a reason why I thought we need two symbols for a feature.
For example, USE_GPFS_FS
That could be a reason why I thought we need two symbols for a feature. For
example, USE_GPFS_FSAL could be used at cmake command line and GPFS_FSAL
could be used in the option().
Can't we use this option() inside conditionals?
regards, malahal.
On Thu, Mar 22, 2018 at 8:43 PM, Daniel Gryniewicz
I don't think this works because of option(). This defines the value to
it's default (OFF if no default is given), so the value is always
defined. We can skip using option, but this will break anyone using any
tools to automate their cmake.
What we need is for option() to distinguish between
Here is what I wanted. Let us say there is a compilation feature called
USE_FSAL_GPFS. I want these possibilities:
1. If I enable this feature at the "cmake command line", enable this. If it
can't be enabled due to missing packages, then please fail cmake!
2. If I disable this feature at the "cmak
That's true, you can "make rpm". However, by default it will make
exactly what your cmake decided should build, so it will still silently
turn off features based on lack of dependencies. If you have you're own
rpmbuild command line using the spec file and appropriate --enable
options, it shou
I've grown to prefer building RPMs (or to a lesser extent .debs).
Dependencies (RPM BuildRequires: or dpkg Build-Depends:) are explicitly
named. If you don't have them installed, you can't build.
Any magic steps that are necessary are documented in the packaging
file(s); you don't have to remember
So, there is an option STRICT_PACKAGE that is supposed to enable this.
It's not fully utilized, but it's mostly there.
The problem is that we can't tell whether the default is being used
(lots of options are on by default but disable themselves if the
packages aren't installed) or if the user
If I specify an option on the cmake command line, I would like it to be
honoured, if not, simply fail. Today, cmake only gives a warning if it
can't meet my option's requirements. Can some cmake guru fix this first?
On Tue, Mar 20, 2018 at 8:38 PM, Daniel Gryniewicz wrote:
> It's probably a goo
It's probably a good idea to add the build options to --version
output, or something. That way we can ask for it in these types of
situations. I've added a card to the wishlist for this.
Daniel
On Tue, Mar 20, 2018 at 9:39 AM, TomK wrote:
> On 3/19/2018 9:54 AM, Frank Filz wrote:
>>>
>>> Solve
On 3/19/2018 9:54 AM, Frank Filz wrote:
Solved.
Here's the solution in case it can help someone else.
To get a certain feature in NFS Ganesha, I had to compile the V2.6
release from source. When configuring to compile, idmapd support got
disabled since packages were missing:
libnfsidmap-devel
> Solved.
>
> Here's the solution in case it can help someone else.
>
> To get a certain feature in NFS Ganesha, I had to compile the V2.6
> release from source. When configuring to compile, idmapd support got
> disabled since packages were missing:
>
> libnfsidmap-devel-0.25-17.el7.x86_64
>
>
On 3/17/2018 1:15 AM, TomK wrote:
On 3/7/2018 9:15 AM, Frank Filz wrote:
With the idmapd service disabled, the UID / GID for folders is still
nobody.
Now Malahal mentioned that only the idmapd libraries are being used by
NFS Ganesha but the service can be off. So does this imply that perhaps
On 3/7/2018 9:15 AM, Frank Filz wrote:
With the idmapd service disabled, the UID / GID for folders is still
nobody.
Now Malahal mentioned that only the idmapd libraries are being used by
NFS Ganesha but the service can be off. So does this imply that perhaps
default values for Domain are get
On 3/8/2018 8:42 AM, TomK wrote:
I take this comment back:
"I think the FreeIPA client is using it instead. Thinking it's not an
NFS Ganesha question at this point then."
If NFS Ganesha uses only some of the idmapd libraries, does this imply I
should be looking at the NFS Ganesha configs to
On 3/8/2018 2:38 AM, Malahal Naineni wrote:
Hmm. When I change some configs in /etc/idmapd.conf on the client:
Nobody-User = nfsnobody
Nobody-Group = nfsnobody
server that connects to the NFS Ganesha cluster, I do see some changes
and folders list as nfsnobody instead of nobody. So that gave
>> Tried identical ifmapd.conf files on client and server but rpcidmapd
tries to start the local copy of nfsd on the nfs Ganesha servers but that
competes with
NFS Ganesha doesn't need rpcidmapd daemon running. So refrain from running
the idmapd daemon. Ganesha uses idmapd libraries, so you should
> On 3/6/2018 10:45 AM, Tom wrote:> t...@my.dom is an ad user. Nix.my.dom
> is a subdomain managed freeipa.
So you have two domains visible on your client? That may be causing confusion.
The client sending t...@my.dom@localdomain makes me think idmapd thinks
localdomain is the domain to use fo
On 3/6/2018 10:45 AM, Tom wrote:> t...@my.dom is an ad user. Nix.my.dom
is a subdomain managed freeipa.
Tried identical ifmapd.conf files on client and server but rpcidmapd tries to
start the local copy of nfsd on the nfs Ganesha servers but that competes with
nfs-Ganesha and won’t bind on p
t...@my.dom is an ad user. Nix.my.dom is a subdomain managed freeipa.
Tried identical ifmapd.conf files on client and server but rpcidmapd tries to
start the local copy of nfsd on the nfs Ganesha servers but that competes with
nfs-Ganesha and won’t bind on port 2049. So I need to change the p
Based on the error messages, you client is not sending t...@nix.my.dom
but is sending t...@my.dom@localdomain. Something is mis-configured on
the client. Have you tried having identical (including case)
idmapd.conf files on both the client and server?
Idmap configuration has historically be
Hey Guy's,
Getting below message which in turn fails to list proper UID / GID on
NFSv4 mounts from within an unprivileged account. All files show up with
owner and group as nobody / nobody when viewed from the client.
Wondering if anyone saw this and what the solution could be here?
If not t
25 matches
Mail list logo
