<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyatta-cfg-system.git/scripts/check-params-on-reboot.d/ipv6_disable_blacklist, branch current</title>
<subtitle>Vyatta system-level configuration templates/scripts (mirror of https://github.com/vyos/vyatta-cfg-system.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=current</id>
<link rel='self' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=current'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/'/>
<updated>2021-06-26T21:13:53+00:00</updated>
<entry>
<title>Debian: remove deprecated vyatta-config-reboot-params script</title>
<updated>2021-06-26T21:13:53+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2021-06-26T21:13:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=e9c470087330f410c9d5dcee98c2c0f6dd0f8c16'/>
<id>urn:sha1:e9c470087330f410c9d5dcee98c2c0f6dd0f8c16</id>
<content type='text'>
Actions are now handled in vyos-router script on startup by calling the vyos-1x
Python handler scripts.
</content>
</entry>
<entry>
<title>* run start-up script vyatta-config-reboot-params very early in boot process</title>
<updated>2011-04-19T01:00:48+00:00</updated>
<author>
<name>Mohit Mehta</name>
<email>mohit@vyatta.com</email>
</author>
<published>2011-04-19T01:00:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=4d5862053ef2f99d09507b2e9b702aca1229099a'/>
<id>urn:sha1:4d5862053ef2f99d09507b2e9b702aca1229099a</id>
<content type='text'>
  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'
</content>
</entry>
</feed>
