<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyatta-cfg-system.git, branch debian/0.19.40</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=debian%2F0.19.40</id>
<link rel='self' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=debian%2F0.19.40'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/'/>
<updated>2011-02-22T18:07:39+00:00</updated>
<entry>
<title>0.19.40</title>
<updated>2011-02-22T18:07:39+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-22T18:07:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=0fed45267a4af54fdc944d45d292798a07fb724e'/>
<id>urn:sha1:0fed45267a4af54fdc944d45d292798a07fb724e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Handle case of device with no active IRQ</title>
<updated>2011-02-21T23:54:21+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-21T23:54:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=78d24daefeab6e91f282044abb8930678434ea8c'/>
<id>urn:sha1:78d24daefeab6e91f282044abb8930678434ea8c</id>
<content type='text'>
Bug 6784
Disabled device has no IRQ, so don't change it.
</content>
</entry>
<entry>
<title>Use standard mechanism to start/stop snmp</title>
<updated>2011-02-18T18:55:50+00:00</updated>
<author>
<name>Stephen Hemminger</name>
<email>stephen.hemminger@vyatta.com</email>
</author>
<published>2011-02-18T18:55:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=c8165a1a29572d7bf78d11c83afd18fff80a02f5'/>
<id>urn:sha1:c8165a1a29572d7bf78d11c83afd18fff80a02f5</id>
<content type='text'>
The net-snmp has snmpd.init script which is installed in standard
place. Invoke it with standard mechanism to avoid any security or
other problems. Also allows debugging snmpd by changing /etc/default/snmp.
</content>
</entry>
<entry>
<title>0.19.39</title>
<updated>2011-02-07T20:24:32+00:00</updated>
<author>
<name>John Southworth</name>
<email>john.southworth@vyatta.com</email>
</author>
<published>2011-02-07T20:24:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=636a269f9a3b4caeac9b5fa7bea360bfba814206'/>
<id>urn:sha1:636a269f9a3b4caeac9b5fa7bea360bfba814206</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'napa' of git.vyatta.com:/git/vyatta-cfg-system into napa</title>
<updated>2011-02-07T20:24:26+00:00</updated>
<author>
<name>John Southworth</name>
<email>john.southworth@vyatta.com</email>
</author>
<published>2011-02-07T20:24:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=bc3658682531c35a4015c46913acfa95972ba77d'/>
<id>urn:sha1:bc3658682531c35a4015c46913acfa95972ba77d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix syslog not reloading properly after changing the log level</title>
<updated>2011-02-07T20:23:24+00:00</updated>
<author>
<name>John Southworth</name>
<email>john.southworth@vyatta.com</email>
</author>
<published>2011-02-07T20:22:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=9d9813280dca4c6657a5570568bae54360f0afbc'/>
<id>urn:sha1:9d9813280dca4c6657a5570568bae54360f0afbc</id>
<content type='text'>
Bugfix 6781
</content>
</entry>
<entry>
<title>0.19.38</title>
<updated>2011-02-03T08:30:03+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-02-03T08:30:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=cf21f8a49f22efcb0a0ce0a99ba2755269320a9b'/>
<id>urn:sha1:cf21f8a49f22efcb0a0ce0a99ba2755269320a9b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bugfix 6773: Spread load of single-queue NICs across all CPUs.</title>
<updated>2011-02-03T08:06:08+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-02-03T08:06:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=c1eb2494559fb0f6ee2beecaedb2a415ff096056'/>
<id>urn:sha1:c1eb2494559fb0f6ee2beecaedb2a415ff096056</id>
<content type='text'>
The initial CPU selection function needs to take hyperthreading
into account.
</content>
</entry>
<entry>
<title>0.19.37</title>
<updated>2011-02-01T18:52:50+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-02-01T18:52:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=82cc765810fb303cecd1ba3167d36d7adbedbfa4'/>
<id>urn:sha1:82cc765810fb303cecd1ba3167d36d7adbedbfa4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bugfix 6156: Allow time for renaming to complete before running biosdevname</title>
<updated>2011-02-01T18:52:23+00:00</updated>
<author>
<name>Bob Gilligan</name>
<email>gilligan@vyatta.com</email>
</author>
<published>2011-02-01T18:27:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyatta-cfg-system.git/commit/?id=a85d727c301007fb6fff667e6899bcbc00d7b2be'/>
<id>urn:sha1:a85d727c301007fb6fff667e6899bcbc00d7b2be</id>
<content type='text'>
It appears that biosdevname can be confused if interface renaming is
being performed by other udev worker processes at the same time that
it is running.  Since vyatta_net_name does protect the body of its
code with a lock, we can be sure that no other renaming will be
started in other udev worker processes while this one is running in
vyatta_net_name.  But renaming being performed by other udev worker
processes that were triggered by previous executions of
vyatta_net_name may still be in progress.  This change gives any
interface renaming that was called for by previous invocations of
vyatta_net_name a chance to complete before we call biosdevname.
(cherry picked from commit 9dd41e8481e84bf80fcb0e9c3d7843c8a0b20059)
</content>
</entry>
</feed>
