vyatta-cfg-system.git/sysconf, branch jennerVyatta system-level configuration templates/scripts (mirror of https://github.com/vyos/vyatta-cfg-system.git)
https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=jenner2009-07-30T20:42:59+00:00Fix 4748: Pre-login message files (/etc/issue,/etc/issue.net) are2009-07-30T20:42:59+00:00Stig Thormodsrudstig@vyatta.com2009-07-30T20:42:59+00:00urn:sha1:cbdcd18b2e5328d24a9dfe04dfa015f8375b50ac
replaced with Debian branding during full-upgrade to Jenner
Bugfix 4592: Generate NTP config file from Vyatta configuration parameters.2009-06-17T22:54:59+00:00Bob Gilligangilligan@vyatta.com2009-06-17T22:54:59+00:00urn:sha1:08d0d9ed2d8824a446bfe6a1ba660db854f1a8f5
This fix changes the way that the /etc/ntp.conf file is generated. Now
it is generated at boot time using a fixed section that contains
only parameters that users don't change, plus a section that is generated
from any "system ntp-servers" parameters that are configured. The fixed
section does not contain any "server" definitions, so all server definitions
come from the Vyatta config.
The Vyatta configuration template for this parameter and code
at other places in the system will now start the NTP server ONLY if
there is at least one NTP server configured. So the user can "turn off"
the NTP server by just deleting all NTP servers from the configuration.
The default "config.boot" file does contiain one built-in "system ntp-servers"
parameter, so a newly installed system will start the NTP server.
Make telnet management smarter2009-06-17T00:48:42+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-06-16T22:31:49+00:00urn:sha1:c6c477f2ffb0f2fd4cf12882f22c2c44ab57cc46
Bug 4591
Consolidate check for telnet login
Don't remove /etc/securetty edit it
Simplify ntp.conf2009-05-24T17:12:29+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-05-24T17:12:29+00:00urn:sha1:8a88cafaef48dbad48aa6732cf0ba540024a11dc
Only put comments in about features that are used.
add iburst2009-05-22T21:27:02+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-05-22T21:27:02+00:00urn:sha1:698795932eeba7dec305433451fce51898e1e3d6Put server at end of file2009-05-22T21:17:08+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-05-22T21:17:08+00:00urn:sha1:5211fe6f4a9e7ae5d15ec7dc8eec231c9d66655b
So when CLI updates ntp.conf, the file stays same format
Add NTP configuration file2009-05-22T15:10:24+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-05-22T15:08:03+00:00urn:sha1:5f836abba30318aa8088037744ed3e2398a39b6c
There are options (like restrict) that should be ntp.conf
This would reduce security exposure of the router (see recent CVE).
Also, this avoid restarting ntp server on boot when using the default
vyatta ntp server.
Resolve problems with syslog.conf2009-04-09T20:23:40+00:00Stephen Hemmingershemminger@vyatta.com2009-04-09T20:23:40+00:00urn:sha1:cc107178eacb42a0c7b324a8aff7217cbc40b35c
Default fallback code was broken
Change to blocked out region for Vyatta config.
Rewrite existing syslog configuration update2009-04-08T22:33:37+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-04-07T04:32:29+00:00urn:sha1:3f6410042b54db636eac390657a8a35583515ce4
Do most of the work in the rewritten vyatta_update_syslog code.
Handle multiple facilities for same target without causing duplicate
log messages.
Never restart syslog daemon, just reload it and only if the configuration
has changed.
Don't double log quagga messages2009-04-01T15:10:36+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-04-01T15:10:36+00:00urn:sha1:d62e5ab7a6cef21d9e0ef3f99bb954460c0299b2
Bug 4205
Duplicate messages in syslog for quagga notice and above messages.