arrrgghh..
as a drop/kick..#test to set the client nfs/mount
192.168.1.45:/cloud_crawl /cloud_crawl nfs defaults 0 0 -o uid=600 -o gid=600
On Fri, Jul 8, 2016 at 3:32 PM, bruce <badouglas@xxxxxxxxx> wrote:
This is for a test internal -- 192.168.1.* group of 3-4 systems. So, there's no real domain, but ....Hey..Yeah, I had seen a few articles that pointed to the idmapd as being a possible issue..On Fri, Jul 8, 2016 at 2:20 PM, Tom Horsley <horsley1953@xxxxxxxxx> wrote:On Fri, 8 Jul 2016 13:57:24 -0400
bruce wrote:
> I know, I could just chown, etc.. after the fact.. but I'd like to figure
> out how it should be done!!
I only know it is the most confusing NFS topic :-). It seems to work
OK if all the machines are getting their users from the same
source (NIS, LDAP, SSSD, something like that). There is some idmapd
thing that turns my brain to cheese when I try to read about it.
I have done desperate things like edit the /etc/idmapd.conf and
set Nobody-User and Nobody-Group to the user I happened to know
I wanted to own files because I could never get any other aspect
of idmapd to work :-(.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org