Well, I don't know why someone else has just marked themselves as
affected by this bug, but the bug is unreproducible and we have no leads
on a solution; so I'm closing it as invalid.
** Changed in: rpcbind (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification becaus
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rpcbind (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026622
Title:
in
The odd thing is I ran the script after installing the packages one-by-one and
it worked OK. Obviously it realised the packages were already installed so
skipped doing anything there, then it set up the various files. However, it was
still a bit slower to come up after reboot than when the comme
I think this is unlikely to be a bug in either rpcbind or network-
manager, but a bug in how your script is configuring things. It's
normal for network-manager to comment out dhcp-only interfaces in
/etc/network/interfaces, and for these network devices to be managed by
network-manager; and rpcbin
It is strange. I have a script to install NIS and autofs, it installs
the following packages:
portmap
nis
tcsh
nscd
autofs
rsh-client
rsh-server
nfs-kernel-server
Then it creates/updates some of the file (auto.master and so on) to suit
out use.
If I install each package in turn and reboot, it co
Actually this is not quite true. It turns out on the next machine that
this change was done earlier (Friday 13th, with interfaces.bak-0 file
having the uncommented line), but it results in the system breaking once
rpcbind, nis, etc has been added.
So before rpcbind & nis is installed, I can reboot
