Bug#621027: Invalid shell option in start-statd

To: Luk Claes <luk@debian.org>
Cc: 621027@bugs.debian.org
Subject: Bug#621027: Invalid shell option in start-statd
From: Marc Glisse <marc.glisse@inria.fr>
Date: Sat, 9 Apr 2011 12:06:05 +0200 (CEST)
Message-id: <alpine.DEB.2.02.1104091201001.2411@laptop-mg.saclay.inria.fr>
Reply-to: Marc Glisse <marc.glisse@inria.fr>, 621027@bugs.debian.org
In-reply-to: <4DA029EF.3080204@debian.org>
References: <4DA029EF.3080204@debian.org>

On Sat, 9 Apr 2011, Luk Claes wrote:

The problem is definitely not related as start-statd is not used in the
init scripts.


Ah, ok, sorry for posting in an unrelated bug then.

Do you have rpcbind installed? Do you still have issues with the latest
upload (1:1.2.3-2)?

No, I appear to have portmap instead. I'll test the new upload (and thusthe switch to rpcbind) when I get back (about 10 days) as I want to benearby when I try it.


Thanks for the answer,

--
Marc Glisse

Reply to:

Follow-Ups:
- Bug#621027: Invalid shell option in start-statd
  - From: Marc Glisse <marc.glisse@inria.fr>

References:
- Bug#621027: Invalid shell option in start-statd
  - From: Luk Claes <luk@debian.org>

Prev by Date: Processed: reassign 619996 to libnfsidmap, forcibly merging 594933 619996
Next by Date: Bug#562737: failed with "Starting NFS common utilities: statd, failed!"
Previous by thread: Bug#621027: Invalid shell option in start-statd
Next by thread: Bug#621027: Invalid shell option in start-statd
Index(es):
- Date
- Thread