summaryrefslogtreecommitdiff
path: root/debian
diff options
context:
space:
mode:
authorBob Gilligan <gilligan@vyatta.com>2008-10-14 13:54:35 -0700
committerBob Gilligan <gilligan@vyatta.com>2008-10-14 13:54:35 -0700
commit6a2393d8053ab9ff9651a6f9c3b243cced7e4439 (patch)
tree581cd52701ac9440f50453001f3c4cdf3271c8b5 /debian
parentaed20563b004d8c274b8a3f72d161cf75bcf4e4c (diff)
downloadvyatta-cfg-system-6a2393d8053ab9ff9651a6f9c3b243cced7e4439.tar.gz
vyatta-cfg-system-6a2393d8053ab9ff9651a6f9c3b243cced7e4439.zip
Bugfix: 3744
When a new member is added to a RAID group that holds the root filesystem, we need to re-install grub so that the new disk will be bootable. But this can only be done after the RAID set has completed rebuilding. Added mechanism that uses the event notification infrastructure of "mdadm" to trigger the re-installation of grub after the rebuild completes.
Diffstat (limited to 'debian')
-rw-r--r--debian/vyatta-cfg-system.postinst.in7
1 files changed, 7 insertions, 0 deletions
diff --git a/debian/vyatta-cfg-system.postinst.in b/debian/vyatta-cfg-system.postinst.in
index 53fa062c..21d7ff32 100644
--- a/debian/vyatta-cfg-system.postinst.in
+++ b/debian/vyatta-cfg-system.postinst.in
@@ -111,6 +111,13 @@ sed -i 's/requisite[ \t][ \t]*pam_securetty.so/required pam_securetty.so/' $root
[ grep "blacklist.*snd-pcsp" >&/dev/null ] || echo "blacklist snd-pcsp" >>/etc/modprobe.d/blacklist
+#
+# Ask mdadm to call our own event handling daemon
+#
+if [ -e /etc/default/mdadm ]; then
+ sed -i 's+^DAEMON_OPTIONS=.*$+DAEMON_OPTIONS="--syslog --program /opt/vyatta/sbin/vyatta-raid-event"+' /etc/default/mdadm
+fi
+
# Local Variables:
# mode: shell-script
# sh-indentation: 4