The 'set +v' is ok.
The command block following it is not.
The problem is caused by the handling of read-only variables in
/etc/bash-completion:
{
# These declarations must go within braces in order to be able to silence
# readonly variable errors.
BASH_COMPLETION="${BASH_COMPLETION
Same problem here, using pxelinux 6.03 as of 16.04.
I initially thought that it failed at an earlier PXE stage, as it alway
booted to the local hard disk (exiting PXE), but that was only due to a
'default harddisk' within the configuration:
default harddisk
timeou
Hi Steve,
I will have a look at #811823 later on, but for a start:
We have /var mounted as a separate partition on all installations
on which we see the idmapd start-up problems. The same goes for
/usr and /tmp.
Cheers,
Alex
On 19/07/11 18:59, Steve Langasek wrote:
> iFred,
>
> I could not rep
Hi Jean,
I can only (temporarily) offer the patched mountall packages we use
on our cluster for just over 400 machines:
http://fias.uni-frankfurt.de/~xela/mountall_2.20.1xela2_amd64.deb
http://fias.uni-frankfurt.de/~xela/mountall_2.20.1xela2_i386.deb
They should work ok on lucid.
For nfs-co
I have invested some time into analysis of some of the problems the
introduction of upstart/mountall created.
Building on Steve Langasek's and Clint Byrum's ideas of introducing
fixes in the start-up procedure to make idmapd/gssd and even statd start
reliably again, I initially failed due to the l
This is a secondary patch meant to prevent miscounting of mounts in
mountall.
The problem may actually already exist in mountall 2.20+nmu1 (the core
of the patch should work there, too).
With asynchronous event handling, this problem may show up severely,
which is why I post it here.
** Patch ad
Suitable for the mountall async patch set just provided, here is my set
of job configuration files for nfs-common:
gssd -- (triggered by portmap and local-filesystems)
gssd-mounting -- (triggered by mounting, triggers gssd)
idmapd -- (triggered by local-filesystems)
idmapd-mounting -- (triggered b
You may also refer to LP #643289 posts #2, #3, #4, which provide fixes
for mountall blocking and for various start-up problems of statd as well
as for idmapd/gssd/rpc_pipefs. Those fixes are based on the above fixes,
but go further to make sure mountall and rpc_pipefs mounting proceed in
proper seq
You may also refer to LP #643289 posts #2, #3, #4, which include (among
others) a fix for gssd start-up problems. Please note that all of #2,
#3, #4 should be applied to make it work.
While I have not tested my gssd fix as intensely as similar ones for
idmapd/statd, all share major functionality,
