EFFECT: This will disable all job log output. This is potentially rather extreme, so users may wish to use work-around 2 below.
= Work-Around 2 =
1) Boot with '--no-log' on kernel command-line.
2) Disable the flush-early-job-log job:
echo manual | sudo tee /etc/init/flush-early-job-log job.override
3) Reboot.
EFFECT: This will throw away data that jobs produce before the disk becomes writeable, which tends to be minimal since only a very few jobs start this early in the boot process.
File /etc/init/flush-early-job-log job.override should be deleted once a fix for this bug is available in Ubuntu.
Work-arounds for this problem:
= Work-Around 1 =
Boot with '--no-log' on kernel command-line.
EFFECT: This will disable all job log output. This is potentially rather extreme, so users may wish to use work-around 2 below.
= Work-Around 2 =
1) Boot with '--no-log' on kernel command-line.
2) Disable the flush-early-job-log job:
echo manual | sudo tee /etc/init/ flush-early- job-log job.override
3) Reboot.
EFFECT: This will throw away data that jobs produce before the disk becomes writeable, which tends to be minimal since only a very few jobs start this early in the boot process.
File /etc/init/ flush-early- job-log job.override should be deleted once a fix for this bug is available in Ubuntu.