On 29/01/2022 11:44, Robert Nichols wrote:
No change:
[fedora ~]# hostnamectl hostname fedora.local
[fedora ~]# hostnamectl
Static hostname: fedora.local
Icon name: computer-vm
Chassis: vm
Machine ID: 6e701e7fa0dc4996984b6509b40eb940
Boot ID: 256c0a3fa9dd4b88bd61145aacc8e106
Virtualization: kvm
Operating System: Fedora Linux 35 (Workstation Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:35
Kernel: Linux 5.15.16-200.fc35.x86_64
Architecture: x86-64
Hardware Vendor: Red Hat
Hardware Model: KVM
[fedora ~]# hostname --fqdn
hostname: Name or service not known
[fedora ~]# hostname
fedora.local
[fedora ~]# mount -t nfs plugh-3g:/srv/shared /Public
[fedora ~]# ll -d /Public
drwxrws--x. 11 nobody nobody 4096 2022-01-28 17:20:50 /Public
[fedora ~]# journalctl SYSLOG_IDENTIFIER=nfsidmap | tail -4
Jan 28 21:19:14 fedora.local nfsidmap[2461]: nss_getpwnam: name 'root@local' does not map into domain 'localdomain'
Jan 28 21:19:14 fedora.local nfsidmap[2463]: nss_name_to_gid: name 'root@local' does not map into domain 'localdomain'
Jan 28 21:19:14 fedora.local nfsidmap[2464]: nss_getpwnam: name 'samba@local' does not map into domain 'localdomain'
Jan 28 21:19:14 fedora.local nfsidmap[2465]: nss_name_to_gid: name 'admin@local' does not map into domain 'localdomain'
A reboot after setting the hostname yields the same result. And, it's not because of anything special about a ".local" domain. Nothing I put in there causes a FQDN to be set.
Interesting. Here:
[root@f35ser ~]# hostnamectl hostname fedora.local
[root@f35ser ~]# exit
logout
[egreshko@f35ser ~]$ su -
Password:
[root@fedora ~]# hostnamectl
Static hostname: fedora.local
Icon name: computer-vm
Chassis: vm
Machine ID: c4783bc505a24a9f973009568932bd82
Boot ID: a98191139f9c4d659faa48e5803d923b
Virtualization: kvm
Operating System: Fedora Linux 35 (Server Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:35
Kernel: Linux 5.15.15-200.fc35.x86_64
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _Q35 + ICH9, 2009_
[root@fedora ~]# hostname --fqdn
fedora.local
[root@fedora ~]# hostname
fedora.local
[root@fedora ~]# mount -t nfs nas:/volume1/homes/djensen /mnt
[root@fedora ~]# ll -d /mnt
drwxrwxrwx. 1 djensen users 288 Sep 26 08:11 /mnt
[root@fedora ~]# journalctl -b 0 SYSLOG_IDENTIFIER=nfsidmap | tail -4
-- No entries --
Now, I did things a bit differently...... Thinking maybe you have nfs-idmapd.service
running and maybe
/srv/shared is a directory with other users below it.
[root@fedora ~]# umount /mnt
[root@fedora ~]# systemctl start nfs-idmapd.service
[root@fedora ~]# mount -t nfs nas:/volume1/homes /mnt
[root@fedora ~]# ll -d /mnt
drwxrwxrwx. 1 root root 76 Sep 26 06:39 /mnt
[root@fedora ~]# ls /mnt
admin djensen egreshko eric yyponpon
[root@fedora ~]# ll /mnt
total 0
drwxrwxrwx. 1 1024 users 10 Dec 16 2019 admin
drwxrwxrwx. 1 djensen users 288 Sep 26 08:11 djensen
drwxrwxrwx. 1 egreshko egreshko 30 Nov 10 20:21 egreshko
drwxrwxrwx. 1 1028 users 10 Dec 18 2019 eric
drwxrwxrwx. 1 1027 users 0 Dec 17 2019 yyponpon
[root@fedora ~]# journalctl -b 0 | grep idmap
Jan 29 14:07:20 fedora.local rpc.idmapd[6264]: Setting log level to 0
Jan 29 14:07:25 fedora.local audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nfs-idmapd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
So, I don't know what/why your system wouldn't perform the same.
And you notice nfs4 is being used.
[root@fedora ~]# mount | grep nas
nas:/volume1/homes on /mnt type nfs4
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=2001:b030:112f:2::f355,local_lock=none,addr=2001:b030:112f::19)
One question then.... What do you get for "host plugh-3g"
nas is in my DNS so I get
[root@fedora ~]# host nas
nas.greshko.com has address 192.168.1.142
nas.greshko.com has IPv6 address 2001:b030:112f::19
--
Did 황준호 die?