vyatta-cfg-system.git/scripts/system, 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-30T21:05:21+00:00Fix 4766: can't set login banners "Can't locate Vyatta/Login/Banner.pm"2009-07-30T21:05:21+00:00Stig Thormodsrudstig@vyatta.com2009-07-30T21:05:21+00:00urn:sha1:ad2cdb65e9869c4a78c5ccb3b7fb0d6cfebe5e4aBugfix 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
Fix generation of syslog host targets2009-06-03T18:21:18+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-06-03T18:21:18+00:00urn:sha1:7dc1c900184a629975b2e22e79c5dc44c494448e
Bug 4494
Handle deletion of radius (or other) server2009-06-02T22:54:57+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-06-02T22:54:57+00:00urn:sha1:1151679260e673f69bdb637fec7773b574f3c7b0
The login class manager must be called if login type is deleted.
Also skip updating if no changes to that login type.
Change API for login modules2009-06-02T22:14:08+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-06-02T21:22:15+00:00urn:sha1:37ba59896d4c9ac5c914d1901d86ed7e7d844871
The login modules aren't really objects (if Perl really had objects), so
just use dynamic invoke of update routine.
Make Radius server work2009-06-02T22:14:00+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-06-02T21:08:23+00:00urn:sha1:bf86040fef55fdb644b3670a9e1ec093e67df828
Translate radius-server to Vyatta::Login::RadiusServer
Change how system login update works2009-06-01T22:50:07+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-06-01T22:17:13+00:00urn:sha1:bf4dd2a3dd0f36ebd5c1c7a6a3705d378d0453b2
Use a wrapper script in vyatta_update_login.pl and per login method
objects for the update.
Fix bug preventing 'vyatta' user login.2009-05-31T18:20:26+00:00Stig Thormodsrudstig@vyatta.com2009-05-31T18:20:26+00:00urn:sha1:ba165c0e0cf3929ab29b45468cf550eda771c37dPrint error message on failure to create group/user2009-05-27T20:53:29+00:00Stephen Hemmingerstephen.hemminger@vyatta.com2009-05-27T20:53:29+00:00urn:sha1:c146c4433d10af8a46973b242d48c2aee920dff8
Bug 4448