Closing largely due to confusion generated by the original issue with
/etc/hosts which is not going to be changed due to the usage being
strongly deprecated. Please open new reports for any additional issues
which have been collected on this report.
** Changed in: nis (Ubuntu)
Assignee:
Can this be dealt with more urgently please? It appears to be a low-
hanging fruit: by switching the order of two services, the bug can be
fixed. In our group, we have about 50 machines on NIS/NFS and this bug
is nearly forcing us to consider other Linux distributions. Not worth
it!
--
NIS boot
Kaihsu, please file a new report describing the problem you are
experiencing here. As mentioned earlier in the bug log there are several
issues mixed into this bug report some of which are unlikely to ever get
fixed (like the use of /etc/hosts via NIS). Probably the clearest thing
is to close this
Related?: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/152794
--
NIS boot after mount NFS.
https://bugs.launchpad.net/bugs/26717
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
mortenkjeldgaard : There are several issues wrapped up in this report.
The problem with ordering WRT /etc/hosts has not been fixed nor is it
likely to be.
--
NIS boot after mount NFS.
https://bugs.launchpad.net/bugs/26717
You received this bug notification because you are a member of Ubuntu
I was hit by this today. It seems the bug has been fixed from upstream,
but _unless_ you run dpkg-reconfigure nis you will not realize that the
bug has been fixed. It seems the reconfiguration should take place when
the package is being updated.
--
NIS boot after mount NFS.
** Changed in: nis (upstream)
Status: Fix Committed = Fix Released
--
NIS boot after mount NFS.
https://bugs.launchpad.net/bugs/26717
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: nis (upstream)
Status: Unconfirmed = Fix Committed
--
NIS boot after mount NFS.
https://bugs.launchpad.net/bugs/26717
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
It is unlikely that the hosts issue will be fixed (it applies to more
than just NFS): use of NIS for host name resolution is fairly strongly
deprecated and I would expect that users with such a configuration will
not find reordering the init scripts as local configuration a
significant obstacle.
** Changed in: nis (upstream)
Status: Unknown = Unconfirmed
--
NIS boot after mount NFS.
https://launchpad.net/bugs/26717
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: Debian Bug tracker #163116
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=163116
** Also affects: nis (upstream) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=163116
Importance: Unknown
Status: Unknown
--
NIS boot after mount NFS.
11 matches
Mail list logo