diff options
| author | Mohit Mehta <mohit@vyatta.com> | 2011-04-18 18:00:48 -0700 |
|---|---|---|
| committer | Mohit Mehta <mohit@vyatta.com> | 2011-04-18 18:00:48 -0700 |
| commit | 4d5862053ef2f99d09507b2e9b702aca1229099a (patch) | |
| tree | a3be28fccf256210728f675c0f366fdfc6eebcfa /debian/vyatta-cfg-system.postrm | |
| parent | 2b7d3fef5077dbc28e39ddb6a267fe6ddeb5813b (diff) | |
| download | vyatta-cfg-quagga-4d5862053ef2f99d09507b2e9b702aca1229099a.tar.gz vyatta-cfg-quagga-4d5862053ef2f99d09507b2e9b702aca1229099a.zip | |
* run start-up script vyatta-config-reboot-params very early in boot process
This script executes scripts lying in the following directory:
/opt/vyatta/bin/sudo-users/check-params-on-reboot.d
Scripts in check-params-on-reboot.d are intended for parameters
that require a reboot to take effect after they are set/changed.
Because of the reboot requirement, underlying value and related
config paramter value can become out-of-sync in couple of cases:
1. change parameter value, don't save config, reboot. Underlying
value is different than the value in config file.
2. install new image; when new image boots, underlying value is
the default Vyatta shipped value not the value in config file.
More info: http://bugzilla.vyatta.com/show_bug.cgi?id=6915#c1
This check-in also adds ipv6_disable_blacklist script in
check-params-on-reboot.d to fix the above mentioned problem
for 'system ipv6 disable' and 'system ipv6 blacklist'
Diffstat (limited to 'debian/vyatta-cfg-system.postrm')
| -rw-r--r-- | debian/vyatta-cfg-system.postrm | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/debian/vyatta-cfg-system.postrm b/debian/vyatta-cfg-system.postrm index 89d919ce..413780b5 100644 --- a/debian/vyatta-cfg-system.postrm +++ b/debian/vyatta-cfg-system.postrm @@ -3,6 +3,7 @@ if [ "$1" = "purge" ]; then sed -i -e '/### BEGIN VYATTA/,/### END VYATTA/d' /etc/sudoers sed -i -e 'g/^password/d' /etc/pam.d/password + update-rc.d vyatta-config-reboot-params remove fi # Local Variables: |