vyatta-cfg-system.git/scripts/system, branch pacificaVyatta 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=pacifica2012-09-19T18:48:03+00:00Set hostname after updating hosts file2012-09-19T18:48:03+00:00James Davidsonjames.davidson@vyatta.com2012-09-19T18:48:03+00:00urn:sha1:ea19fe6d0b149bc50858425af4fd953dd780b18d
Fixes bug 8380
Update /etc/hosts when host name and domain name changes2012-09-10T16:11:42+00:00James Davidsonjames.davidson@vyatta.com2012-09-10T16:11:42+00:00urn:sha1:c087276ca0827d7a58c93c9c7683af7311ef5c58Configure logrotate to maintain log file ownership2012-09-05T01:28:12+00:00James Davidsonjames.davidson@vyatta.com2012-09-05T01:28:12+00:00urn:sha1:288ab75d4f2aed39e8993d82f127e6e9dc16b973
logrotate needs the create config option so that it keeps the
original log file's permissions and ownership.
Fixes bug 8240
Use rsyslog to trigger log rotation2012-04-18T18:04:44+00:00James Davidsonjames.davidson@vyatta.com2012-04-06T00:52:08+00:00urn:sha1:2415dea5aa5ecc1542b3da7795c0b7c49b98f259
The previous implementation of log rotation used an hourly cron job to
check log file size and possibly perform a rotation. If the logging
rate is high, this interval may allow for root file system space
exhustion.
Utilizing rsyslog's outchannel mechanism enables log rotation to be
initiated as soon as the log file becomes larger than its configured
size.
Fixes Bug 7807.
Fix server property option2012-02-21T21:19:31+00:00Stephen Hemmingershemminger@vyatta.com2012-02-21T21:19:31+00:00urn:sha1:5f583fe81fc8be7f9e516044b43f3f28037242c8
Bug 7623
Patch provided by Stig.
interfaces: don't add config for missing devices2011-12-22T01:32:51+00:00Stephen Hemmingershemminger@vyatta.com2011-12-22T01:32:51+00:00urn:sha1:537585b5e1a7d73f7c88b7726d0c1f112329bea3
If device disappears or is renamed between the time udev script
is run, and the vyatta-router script is run; then don't add an entry
to the config file.
Fix perl deprecated warning with 5.142011-11-22T19:24:54+00:00Stephen Hemmingershemminger@vyatta.com2011-11-22T19:24:54+00:00urn:sha1:dcff7e2c90f21cc7eb7e08ca054c8779dc0b22fd
Code of the form:
for $i qw(a b c)
causes the warning:
Use of qw(...) as parentheses is deprecated
irq-affinity: more fixup2011-05-20T18:09:55+00:00Stephen Hemmingershemminger@vyatta.com2011-05-20T18:08:20+00:00urn:sha1:c6430d1e9b511e36f59b5b5a484b7edf829be117
1. Fix thread_per_core -- now a global variable
2. Add documentation about where still broken with offline cpus
3. Break out hamming weight function (might be used to fix #2)
Tested on UP, 4 core x 2 thread, 8 socket (virt) and Multiqueue
and single queue NIC.
irq-affinity: use sysfs to read cpu topology2011-05-20T15:38:57+00:00Stephen Hemmingershemminger@vyatta.com2011-05-20T15:27:02+00:00urn:sha1:c206df7d62af7b1c2f310e546c877c18095bc6d1
Change to using sysfs to read cpu topology. This makes code more
robust and follow the standard practice of other utilities.
As an added benefit, irq-affinty now handles offline cpu's and
other cases where cpu numbers are not fully populated.
irq-affinity: initialize sockets to 12011-05-20T14:13:50+00:00Stephen Hemmingershemminger@vyatta.com2011-05-20T14:13:50+00:00urn:sha1:5a1d4ee6db359887ad5b65150fa5de7312a06202