Public bug reported:
Simple RPC programs will not work without running rpcbind in insecure
mode (rpcbind -i). The error that is given when running the RPC server
is:
Cannot register service: RPC: Authentication error; why = Client credential too
weak
unable to register (SIMP_PROG,
Public bug reported:
We have an issue with Upstart not restarting the autofs job when the
automount process dies, and the Upstart job status gets stuck in the
stop/starting state. The process is not automatically restarted by
Upstart like it is supposed to. Trying to manually control the job
The attached patch removes the -p option from the shebang line of
/etc/security/namespace.init and fixes this bug. The effect of the -p
option with bash is to not reset the effective UID to match the real UID
if they are different, but this is the default behavior if bash is
invoked as /bin/sh.
Public bug reported:
When PAM is configured to use pam_namespace.so, something, presumably
PAM, emits the line /bin/sh: 0: Illegal option -p once for every entry
defined in /etc/security/namespace.conf. Switching /bin/sh from dash to
bash using dpkg-reconfigure dash avoids the problem.
I have
Public bug reported:
A syntax error in the pre-start script of /etc/init/sssd.conf prevents
sssd from starting when /bin/sh is implemented by bash instead of dash.
dash seems to ignore the invalid character whereas bash seems to be
sensitive to it and gives the following error:
/bin/sh: -c: line
Sorry, the last diff format was -n. diff -u attached.
** Patch added: sssd.conf.diff
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1081350/+attachment/3439904/+files/sssd.conf.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Patch to /etc/init/sssd.conf is attached.
** Patch added: sssd.conf.diff
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1081350/+attachment/3439903/+files/sssd.conf.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am unable to unmount NFS (v3 or v4) mount points if they were mounted
using the server's IPv6 address instead of the server's hostname (which
resolves to an IPv6 address). umount says mountpoint was not found
in /proc/mounts even though the file system is clearly mounted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000202
Title:
Unable to unmount NFSv3 or NFSv4 mounts when mounted using IPv6
address
To manage notifications about this bug go to:
Public bug reported:
The package libboost-mpi-dev exists in the universe repository for
lucid, but depends on package libboost-mpi1.40-dev which does not exist
in any repository.
$ sudo apt-get install libboost-mpi-dev
Reading package lists... Done
Building dependency tree
Reading state
** Tags added: apport-collected
** Description changed:
We have encountered this bug, http://www.spinics.net/lists/linux-
nfs/msg17801.html, which was discussed on the linux-nfs mailing list in
December 2010. I am reporting the bug here because the discussion on
the linux-nfs mailing
Public bug reported:
We have encountered this bug, http://www.spinics.net/lists/linux-
nfs/msg17801.html, which was discussed on the linux-nfs mailing list in
December 2010. I am reporting the bug here because the discussion on
the linux-nfs mailing list seems to have fizzled out and resulted in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849549
Title:
NFSv4 stat(2) incorrect
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/844336
Title:
snmpd launched before network is fully up
To manage notifications about this bug go to:
Public bug reported:
If /etc/snmp/snmpd.conf contains hostnames which must be resolved using
DNS, snmpd will not be able to resolve those hostnames and seems to
ignore those entries. In most cases, DNS is available and this would
not be an issue. However, when the system is booted, the snmpd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844336
Title:
snmpd launched before network is fully up
To manage notifications about this bug go to:
Public bug reported:
If /etc/snmp/snmpd.conf contains hostnames which must be resolved using
DNS, snmpd will not be able to resolve those hostnames and seems to
ignore those entries. In most cases, DNS is available and this would
not be an issue. However, when the system is booted, the snmpd
17 matches
Mail list logo
