linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de>
To: linux-nfs@vger.kernel.org
Subject: conflicting requirements betweenn rpc.rquotad and nfs services
Date: Sun, 2 Sep 2018 21:01:47 +0200	[thread overview]
Message-ID: <201809022101.49019.ulrich.gemkow@ikr.uni-stuttgart.de> (raw)

Hello,

we updated to Ubuntu 18.04 on our servers and encounter the following
new problem:

We have no IPv6 interfaces/adresses configured and rpc.rquotad complains
about this and refuses to start - it seems the libtirpc has IPv6 as
a requirement when listed in /etc/netconfig.

When commenting out the v6-related lines in /etc/netconfig, rpc.rquotad
starts.

But without the IPv6 related lines in /etc/netconfig rpcbind no longer
starts and emits error messages which seems a little bit weired.

The services start when we start rpc.rquotad with the v6-lines in
/etc/netconfig commented out and using the original version with the
other services.

Is it intended that rpcbind does not start when /etc/netconfig does
not contain the IPv6-lines? Is there a reason for this?

rpc.rquotad --version says

Quota utilities version 4.03.
Compiled with: USE_LDAP_MAIL_LOOKUP EXT2_DIRECT HOSTS_ACCESS RPC RPC_SETQUOTA BSD_BEHAVIOUR

rpcbind seems to emit no version information

Thanks in advance and best regards

-Ulrich

-- 
Ulrich Gemkow
University of Stuttgart
Institute of Communication Networks and Computer Engineering (IKR)

                 reply	other threads:[~2018-09-02 23:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201809022101.49019.ulrich.gemkow@ikr.uni-stuttgart.de \
    --to=ulrich.gemkow@ikr.uni-stuttgart.de \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).