Public bug reported:
I can't find any package that /etc/nsswitch.conf belongs to, so I'm
reporting this issue here since it's related to automount.
I use NIS to distribute automount databases, and the autofs5 package.
My /etc/auto.master file contains:
+auto.master
and I can run "ypcat -k auto.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/1040846
Title:
Missing content in /etc/nsswitch.conf causes failure
To manage notifications about this bug go to:
https://bugs.launchp
Steve's comment #18 is not correct. Automount was first created in the
late 1980's, and when Sun released the first version of name service
switch in the early 1990's, it was already being used to manage
automount maps. Automount maps have been considered a standard, basic
name service ever sinc
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
Please undo the "duplicate" status of this bug.
This bug still exists in Precise 12.04 and 12.04.1: when I start my
system autofs cannot see any maps that are stored in NIS.
--
You received this bug notificat
Public bug reported:
A long time ago I reported a bug in the autofs package:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/111612
That bug was fixed, but now I've discovered that the same bug still
exists in the autofs5 package. Please see the above bug for the issue
and the fix (I appli
FYI, just discovered that the fix made here for autofs4 was never
applied to autofs5, and the same bug exists there; filed:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/912030
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to a
** Bug watch added: Red Hat Bugzilla #782169
https://bugzilla.redhat.com/show_bug.cgi?id=782169
** Also affects: autofs5 (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=782169
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a mem
Manager doesn't wait for NIS to start before starting
# autofs, so we have no maps. Restart it.
#
# Install with:
# sudo cp ~/Downloads/reautofs /etc/init.d
# sudo update-rc.d reautofs defaults 99
#
#
# Author: Paul Smith
start () {
nohup /bin/sh -c '
while true; d
Public bug reported:
Binary package hint: dnsmasq
Looking at the /etc/init.d/dnsmasq file I see a bug; in the start()
function it says:
${DNSMASQ_INTERFACE:+ $DNSMASQ_INTERFACES} \
This is wrong; the variable names should both be the same. Assuming the
right variable name is DN
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
Chuck, can you please undo the "duplicate" status of this bug? This is
NOT a duplicate of bug 50430
--
Autofs fails to start with maps from NIS
https://bugs.launchpad.net/bugs/213574
You received this bug not
I found this bug, I think. We're getting identical problems causing
Evolution Exchange to crash. The problem is ldap is accessing memory
after it's been freed.
Here's the Gnome bug with lots of backtraces and some valgrind logs I
used to figure it out:
http://bugzilla.gnome.org/show_bug.cgi?id=
*** This bug is a duplicate of bug 215904 ***
https://bugs.launchpad.net/bugs/215904
This is really a bug in openldap which is causing lots of ldap-based
apps to fail. There is more info in ubuntu bug #215904
** This bug has been marked a duplicate of bug 215904
(ITS#5518) Assertion error
Marked Evolution Exchange bug as a duplicate.
--
(ITS#5518) Assertion error in io.c:234: ber_flush2
https://bugs.launchpad.net/bugs/215904
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap2.3 in ubuntu.
--
Ubuntu-server-bugs mail
I've loaded up these libraries to test the Evo Exchange crasher.
Unfortunately there was no reliable way to reproduce it; you just had to
do lots of work and eventually it would happen. However, I've added a
debugging message to the code so that I'll know when I've hit a point
where it SHOULD have
This is unquestionably a bug in the Ubuntu SWAT package. If you can't
log into SWAT as an administrator on a standard Ubuntu system, then the
package is broken.
Not only that, but the Importance level of "Low" is wrong, since the
package is not functional as installed.
If the SWAT developers can
The bug is in the libldap package. When you get a new version of that
(which I believe is out now, even for the standard repositories) then
all applications that use LDAP (including Evolution, xscreensaver,
Apache, etc.) will use it and have the fix.
There's no need for a new Apache package, beca
This is still in -proposed? I think it's pretty clear what this bug is
and that it's fixed by the update; we've had a number of people testing
it and reporting success already. Plus, if you look at the actual
patch, it's pretty clear that it fixes the problem.
IMHO this should get promoted out o
Sorry, I didn't realize people were waiting for me. I have no recipe
for reliably reproducing the problem using Evolution so I can't be 100%
sure that it's been fixed. However, I've been using the fix since Chuck
posted his PPA version on 23 May, and -proposed version since it was
uploaded, and I
This might be a problem but I don't see how it proposes to fix bug
#90681 unless we can modify every application, including 3rd party VPN
tools, that want to change /etc/resolv.conf to use NetworkManager to do
it instead of modifying the file directly.
Here's a hint, though: we can't do that :-).
I hit this too; my company uses Juniper's NetworkConnect and it adds its
own DNS servers as the first ones to search to /etc/resolv.conf. I
disabled the download of the DNS server info altogether which is
obviously not optimal, but works OK for me because I've installed a
Linux image on my Linksys
I guess I misunderstood your comment.
IMO, bug #90681 has no relationship to NetworkManager at all. It could
be that the system in 90681 has disabled NetworkManager altogether and
is using raw dhclient; that bug would still happen. The problem that
the dhclient-script overwrites /etc/resolv.conf
Public bug reported:
I filed a bug against the "nis" package that they don't provide any
dhclient-exit-hooks.d hook scripts to handle nis-domain/nis-servers
/nisplus-domain/nisplus-servers DHCP options:
https://bugs.launchpad.net/bugs/246322
I also suggested that they need to modify the dhclient.
Hrm, I just filed a bug about this under the "ntp" package:
https://bugs.launchpad.net/bugs/246314
Note that the ntp package DOES come with dhclient-exit-hooks.d scripts
to turn on/off NTP servers at appropriate times. As this bug mentions,
all that's missing are the entries in dhclient.conf... w
Note you need both nis-servers AND nis-domain. And, there's nisplus-
domain and nisplus-servers as well.
I opened a separate bug for NIS; the request for the "nis" package to
create appropriate dhclient exit hooks is bug #246322
The bug for dhcp3-client to add these to dhclient.conf is bug #2463
After I filed this I realized there was no facility for updating
dhclient.conf via dpkg scripting, so I also filed bug #246343 to have
these fields added to the dhclient.conf "request" line by default. It
won't hurt anything to have them requested there: if they're not
available from the server th
*** This bug is a duplicate of bug 50430 ***
https://bugs.launchpad.net/bugs/50430
On Tue, 2009-10-13 at 18:16 +, Chuck Short wrote:
> *** This bug is a duplicate of bug 50430 ***
> https://bugs.launchpad.net/bugs/50430
>
> ** This bug has been marked a duplicate of bug 50430
>NIS
Is anyone ever going to do anything about this? I know it's not an easy
problem but there are solutions here which will help at least some of
the people and which are not harmful (for example, not updating
/etc/resolv.conf on RENEW if the old nameserver is still present).
If we could do at least
I'm not sure why you think retrieving domain info from the DHCP server
will do anything to help the problem, which is that the Ubuntu DHCP
client is overwriting the resolv.conf file and replacing nameservers
that were added due to VPN connections.
--
resolv.conf overwritten using VPN/PPP etc...
h
I believe this is a duplicate of Bug #1386869
There's a workaround in the comments of that bug. HTH!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1387459
Title:
autofs stops work
This appears to be a bug in the version of autofs that Ubuntu is
shipping. See this report from ArchLinux:
https://bugs.archlinux.org/task/38379
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.n
Also there's a problem reported in Fedora against 5.0.7, but apparently
still present for 5.0.8:
https://bugzilla.redhat.com/show_bug.cgi?id=1038356
** Bug watch added: Red Hat Bugzilla #1038356
https://bugzilla.redhat.com/show_bug.cgi?id=1038356
--
You received this bug notification because
Is there a reason we can't just go get the patches that Ian Kent already
provided for Fedora (see my link to the Red Hat bugzilla entry, which
contains references to RPM versions that fix the problem) and apply them
here and/or in Debian since the bug exists there as well?
--
You received this bu
32 matches
Mail list logo
