=== jstevewhite is now known as stwhite
=== stwhite is now known as jstevewhite
=== JanC_ is now known as JanC
[06:04] <kklimonda> are there any http://cloud-images.ubuntu.com mirrors on the US west coast? I'm seeing transfer speeds of 200-300KB/s using the main location
[06:09] <lordievader> Good morning
=== elky is now known as el
=== jelly-home is now known as jelly
[09:50] <albech> is there anything like selinux on ubuntu installed by default that could prevent connections to localhost services?
[10:07] <lordievader> Apparmor
[10:11] <albech> lordievader: can it be completely disabled for troubleshooting?
[10:49] <lordievader> No idea, sorry. My knowledge beyond the name is severely limited.
[10:56] <rbasak> albech: yes
[10:57] <rbasak> albech: https://help.ubuntu.com/community/AppArmor
[10:57] <rbasak> Complain mode is sufficient for troubleshooting (then it won't actually block stuff)
[12:48] <Odd_Bloke> kklimonda: I don't believe that there are, I'm afraid. :(
=== albech1 is now known as albech
=== albech1 is now known as albech
[15:01] <rbasak> nacc: what does it mean for importer.py:_update_devel_branches to be called with spi=None?
[15:04] <nacc> rbasak: i believe it is only used by --fixup-devel
[15:04] <nacc> rbasak: which can be dropped when we reimport
[15:07] <rbasak> nacc: I don't understand what _update_devel_branches is defined to do. I mean it obviously updates the devel branches, but under what circumstances does it do what?
[15:08] <rbasak> nacc: I'm here because I'd like to see what happens if the devel branches are also hard reset instead of extra merge commits added.
[15:08] <nacc> rbasak: can we chat in the standup? or just after onn irc? nneed to make coffee
[15:08] <rbasak> Sure
[15:09] <rbasak> I'm having dinner straight after the standup but can reappear after that.
[15:11]  * genii 's ears perk up at the mention of coffee, goes to make a pot
[15:13] <nacc> genii: :)
[15:13] <nacc> rbasak: thakns
=== albech1 is now known as albech
=== JanC_ is now known as JanC
[18:50] <keithzg> Huh, well that's weird, I updated a fileserver that hasn't been touched in a while and now resolv.conf isn't listing anything
[18:51] <keithzg> (updated and rebooted, I should say)
[18:52] <keithzg> I swear, resolvconf is more trouble than its worth :P
[18:55] <sionronin> keithzg, yep pretty sure resolv.conf gets reloaded after each reboot
[18:56] <sionronin> that or dhcp or some other service writes on reboot
[18:56] <sarnold> I think we're ditching resolvconf for future releases, no?
[19:07] <keithzg> sarnold: Oh, is it going to be handled by some systemd component or such? (Hopefully better than time is :/)
[19:08] <keithzg> sionronin: Oh yeah, definitely. Just normally it writes out some values, rather than merely the header which states that it was written out, hah, which isn't terribly helpful then
[19:12]  * keithzg is gonna reboot the server once people are home for the day and see if it happens again, then investigate further if so
[19:58] <keithzg> Boy, I do love unattended-upgrades, it really does make a sysadmin's life a lot easier :)
[20:02] <notdaniel> i hope that was sarcasm
[20:04] <dpb1> keithzg: :)
[20:09] <keithzg> It legitimately wasn't sarcasm!
[20:10] <keithzg> I can always disable unattended-upgrades if I want to, but I tend to at *least* put it to install security updates automatically.
[20:10] <notdaniel> i'm sure it is a great thing most of the time
[20:10] <notdaniel> it however was the bane of my existence for a while on aws
[20:11] <keithzg> fair enough
[20:11] <keithzg> I'll admit I don't have it enabled on my one EC2 instance
[20:13] <keithzg> All the little KVM guests at work, though, it just makes 'em hassle free
=== davidbowlby is now known as davidbowlby-afk