Skip to content

Add request-key.d/id_resolver.conf to shut up logspam #297

Merged
merged 1 commit into from
Jan 20, 2023

Commits on Jan 19, 2023

  1. Add request-key.d/id_resolver.conf to shut up logspam

    NFS clients of a kernel before 5.15.89.mx64.445 try to use the
    id_resolver for sec=mariux mounts when uid or gid file attributes are
    transmitted to the server (e.g. when chown or chgrp is done).
    
    The kernel nfs clients makes a user space upcall via /sbin/request-key
    for a key of a type id_resolver and a key description like "user:130" or
    "group:125".
    
    As keys of the type id_resolver are not configured in
    /etc/request-key.conf, this will fail but /sbin/request-key logs
    "request-key: Cannot find command to construct key..." to its stdout
    which ends up in the syslog.
    
    The nfs clients continues by sending the uid/gid value numerically to
    the nfs server, which is what we want.
    
    Configure a (negative) request-key response for keys of the type
    id_resolver to avoid logfile spam.
    
    Kernels since 5.15.89.mx64.445 don't need that, because the userspace
    upcall is avoided for sec=mariux just the same as it is for sec=sys.
    donald committed Jan 19, 2023
    Configuration menu
    Copy the full SHA
    4145b91 View commit details
    Browse the repository at this point in the history