Bug#612481: fai-client: diversion of /etc/init.d/nis during install breaks boot order and autofs

On Mittwoch, 9. Februar 2011, Michael Tautschnig wrote: Which means that it breaks unrelated software (in a non-obvious way, i.e., the installation finishes just fine), which has a well-defined severity level. I have no idea why the severity was downgraded (and not upgraded). No kidding.

Bug#612481: fai-client: diversion of /etc/init.d/nis during install breaks boot order and autofs

Hi Jens, On Dienstag, 8. Februar 2011, Jens Dreger wrote: nis based automount maps don't work after fresh install due to the diversion of /etc/init.d/nis in /usr/lib/fai/updatebase: this affects system installed with fai, correct? (And not the fai installation client itself..) cheers,

Bug#612481: fai-client: diversion of /etc/init.d/nis during install breaks boot order and autofs

Hi Jens, On Dienstag, 8. Februar 2011, Jens Dreger wrote: nis based automount maps don't work after fresh install due to the diversion of /etc/init.d/nis in /usr/lib/fai/updatebase: this affects system installed with fai, correct? (And not the fai installation client itself..)

Bug#612481: fai-client: diversion of /etc/init.d/nis during install breaks boot order and autofs

Package: fai-client Version: 3.4.7 Severity: important nis based automount maps don't work after fresh install due to the diversion of /etc/init.d/nis in /usr/lib/fai/updatebase: fai-divert -a /etc/init.d/nis /sbin/start-stop-daemon /usr/sbin/policy-rc.d this leads to autofs being started

Bug#612481: fai-client: diversion of /etc/init.d/nis during install breaks boot order and autofs

Severity: important I think it's a normal bug. Removing the diversion of /etc/init.d/nis from /usr/lib/fai/updatebase fixes the problem. I have to check if the diversion is not needed any more, or if fai should use policy-rc.d to keep nis from starting during installation.