Skip to content
Snippets Groups Projects
  • Emanuele Aina's avatar
    17ecfc74
    ospack: Disable fqdn resolution for sudo · 17ecfc74
    Emanuele Aina authored
    When opening a new session sudo tries to resolve the fqdn of the host, but that
    introduces a sensible delay if the host does not have a fqdn set up
    appropriately, as it is often the case with development board or when booting
    images in QEMU.
    
    We currently also ship libnss-myhostname which in theory could solve the issue
    at the system level and not just for sudo, but upstream configures it to come
    *after* dns resolution to avoid breaking `hostname --fqdn`, see
    https://github.com/systemd/systemd/issues/1280
    
    
    
    Our use-case is sligthly different and we may configure libnss-myhostname to
    precede dns resolution, but in the meantime keep disabling this in sudo as the
    apertis-customization package used to do.
    
    Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
    17ecfc74
    History
    ospack: Disable fqdn resolution for sudo
    Emanuele Aina authored
    When opening a new session sudo tries to resolve the fqdn of the host, but that
    introduces a sensible delay if the host does not have a fqdn set up
    appropriately, as it is often the case with development board or when booting
    images in QEMU.
    
    We currently also ship libnss-myhostname which in theory could solve the issue
    at the system level and not just for sudo, but upstream configures it to come
    *after* dns resolution to avoid breaking `hostname --fqdn`, see
    https://github.com/systemd/systemd/issues/1280
    
    
    
    Our use-case is sligthly different and we may configure libnss-myhostname to
    precede dns resolution, but in the meantime keep disabling this in sudo as the
    apertis-customization package used to do.
    
    Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>