Sorry for the late response. From what I can see we don't really
implement any dependency chain when configuring NFS/Kerberos on Ubuntu.
We haven't seen this issue in earlier releases of Ubuntu (20.04 and
earlier) though. But seems like the process worked differently at that
point since /etc/nfs.co
I can add more information on Monday when I'm working again. I suspect
we found this issue because it was manually developed/tested to ensure
that everything works. That is without going through the normal
provisioning chain.
As part of our provisioning chain one step is usually to restart the
sys
We're using Puppet to configure our systems and one of the steps is to
ensure gss-rpcd.service is up and running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971935
Title:
Invalid pipefs-director
Hello,
You're correct. The use-case is to mount Kerberos secured NFS mount
points. All other configuration is working as expected since after a
reboot (as mentioned earlier) the system in question is able to
successfully mount with krb5.
Thanks.
--
You received this bug notification because you
After restarting the system /run/rpc_pipefs exists because
/run/systemd/generator/run-rpc_pipefs.mount is created and rpc-gssd
works correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971935
Ti
** Description changed:
Ubuntu 22.04 Server
+ Package version: 1:2.6.1-1ubuntu1
Package nfs-common/nfs-utils provides /etc/nfs.conf and
/lib/systemd/system/rpc-gssd.service.
/etc/nfs.conf (and seems to be copied from
/usr/share/nfs-common/conffiles/nfs.conf) has the configuration:
...
Public bug reported:
Ubuntu 22.04 Server
Package nfs-common/nfs-utils provides /etc/nfs.conf and
/lib/systemd/system/rpc-gssd.service.
/etc/nfs.conf (and seems to be copied from
/usr/share/nfs-common/conffiles/nfs.conf) has the configuration:
...
[general]
pipefs-directory=/run/rpc_pipefs
...
This is the only way i managed to speed up my "Trackpoint" on HP ZBOOK
15u G6 to a acceptable level.
user1@lab1-w:~$ xinput --list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ALP00
20.04 still has this problem.
I'm on a HP Zbook 15u G6.
It seems that xinput only can handle values of max 1, which in my case
is all to slow.
user1@lab1-w:~$ xinput --list-props 11
Device 'ALP0017:00 044E:121C Mouse':
Device Enabled (180): 1
Coordinate Transformation Matrix (18
