[00:33] <Corey> Ruh roh.
[02:38] <Flannel> yeah, you already said that.
[02:51] <Flannel> No, banlist filling down.
[12:30] <IdleOne> yes floodbot we know
[12:30] <IdleOne> Soon as freenode gets it together we will clear them.
[12:31] <tomaw> where do you need opping?
[12:31] <IdleOne> tomaw: no rush
[12:31] <IdleOne> thanks though :)
[12:31] <tomaw> ok
[12:32] <IdleOne> little surprised the trolls haven't attacked us though
[12:33] <IdleOne> Now that I said that :/
[12:33] <elky> indeed
[12:34] <elky> or staff could help someone get rid of excess stuff now...
[12:35] <elky> tomaw: still there?
[12:35] <tomaw> yup
[12:35] <IdleOne> nah, the ban list is not full yet
[12:35] <Pici> I think opping one of us would probably be a good idea
[12:35] <Pici> just in case.
[12:35] <tomaw> opped Pici
[12:35] <Pici> tomaw: thanks
[12:35] <tomaw> np
[12:36] <elky> now fix the +e list
[12:36] <jrib> Pici: I'll clear out some of my bans, I think I have a few stale ones
[12:36] <elky> which is what half the bans will be i'm guessing
[12:36] <Pici> elky: you want a few random pms from confused users too?
[12:37] <elky> Pici: rww is offering to fix it if we op him up
[12:46] <IdleOne> I think I got all the floodbot bans
[12:53] <elky> you can probably remove all my bans except for the racist one
[13:37] <Pici> restarting ubottu
[16:22] <Pici> tsimpson: you might want to look at pruning the ubottu log, after ubottu.com was klined during the server issues (dunno why), the log file indicated that ubottu was trying to reconnect to freenode a few thousand times a second.
[16:22] <Pici> I had to use the killbot page to get it working again.
[16:31] <tsimpson> Pici: the server was k-lined
[16:31] <tsimpson> apparently
[16:31] <Pici> yes.
[16:32] <tsimpson> I think supybot was just in a while loop
[16:33] <tsimpson> it may even be (another) bug in supybot, as it's supposed to wait
[16:33] <DJones> AlanBell: /w 20
 by having a crazy idea of installing ubuntu
[16:33] <bazhang> rant detected
[16:35] <tsimpson> a threaded while loop at that
[19:36] <popey> Hello!
[19:36] <popey> 14:23:06 -!- meetingology [meetingolo@174.143.202.182] has quit [K-Lined]
[19:37] <popey> uhm.. can we get it back?
[19:38] <Myrtti> someone (AlanBell?) needs to restart it, afaik its been unklined hours ago
[19:38] <DJones> I pinged him a couple of hours back about that, he appears to away for a while
[19:39] <popey> oh, he was flying back from .be I guess
[19:39]  * popey spies via latitude
[19:40] <DJones> popey: is the NSA
[19:40] <popey> hah
[19:40] <popey> thanks!
[19:48] <DJones> Zaku> and I can easily hack ubuntu.com
[19:50] <DJones> Guest8424> DJones, ubuntu.com is vulnerable to a variety of attacks, mainly RFI.
[20:08] <tsimpson> ... I'm going to have to kill the bots for a minute
[20:08] <ikonia> at least there is warning, thank you tsimpson
[20:09] <tsimpson> supybot decided it was fine for the log 22GB
[20:10] <tsimpson> well, one is 22GB, one is 3.5, another is 2.5
[20:11] <tomaw> sounds like a cry for help
[20:13] <DJones> Maybe its the bots list of people to get revenge on for klining it earlier on
[20:13] <ikonia> has ubuntu 13.04 dropped the use of /etc/fstab - thats the 3rd person I've see say "I have no fstab file"
[20:14] <tomaw> DJones: I think that was just them losing at a bot fight
[20:15] <DJones> On this 13.04 machine, I have an /etc/fstab although it is an upgraded from earlier versions
[20:15] <Unit193> Haha!
[20:15] <ikonia> I just don't see how it's possible to not have an /etc/fstab, and it's not like this guy is the first one to say it
[20:16] <Unit193> dpkg-query: no path found matching pattern /etc/fstab Hrm, maybe it's done a different way?
[20:16] <ikonia> they have the /etc/fstab.d directory , but other distros use that too, but not having the fstab.....
[20:17] <ikonia> seems odd, to break such an important standard
[20:18] <DJones> I have a /etc/fstab.d but its empty
[20:18] <ikonia> yes, it's for user mounts
[20:18] <ikonia> so should be empty
[20:19] <ikonia> there are posts all over the internet showing /etc/fstab on 13.04 for example http://askubuntu.com/questions/297069/ubuntu-13-04-hard-disk-does-not-boot
[20:20] <ikonia> never mind, the file is there, this guy just can't read his screen
[20:20] <ikonia> but he's not the first to say that
[20:21] <DJones> Its not the first time this guy has disputed things and swore that black is white
[20:21] <ikonia> oh really
[20:21] <ikonia> I've never seen him before
[20:22] <ikonia> I'm backing away from this, as modifying a file like this when he doesn't pay attention to if the file is even there doesn't interest me
[20:22] <tsimpson> ok, 28GB freed by deleting supybot logs
[20:22] <tsimpson> and the "no space left on device" messages are gone :)
[20:22] <DJones> He was the guy a week or so back that wanted support with cracked software, he swore blind that just because the .rar file he wanted help extracting had '-cracked' in the filename wasn't cracked
[20:23] <ikonia> oh this idiot
[20:23] <ikonia> oh I'm totally out then
[20:23] <DJones> yup
[20:33] <ikonia> someone needs to change that ISO file name from amd64 to 64bit
[20:33] <ikonia> I logged a bug for it and the questions about it never go away
[20:35] <DJones> It always makes me think of hoovers, nobody ever says they're going to dyson the living room carpet, its always hoover, just seems to be something thats been given a name in the past & nobody wants to change it
[20:35] <tsimpson> technically though, it is amd64
[20:35] <ikonia> considering ubuntu is supposed to target user friendly, it's not really the best namies
[20:35] <ikonia> tsimpson: technically fully agree
[20:35] <ikonia> however real world target user position, it's not helpfui
[20:36] <tsimpson> yeah, I accept it's a cause of confusion for 99% of people
[20:36] <DJones> Its a least the 2nd time I've seen the question asked today
[20:38] <ikonia> thats odd, launchpad.net shows me having only logged one bug ??
[20:38] <ikonia> I've logged many
[20:38] <DJones> Would it be as simple as changing the filename, or are there likely to be deep rooted things that would also need changing with the iso
[20:40] <tsimpson> ikonia: it doesn't show fixed released/invalid by default iirc
[20:40] <ikonia> tsimpson: I can't get it to show anything other than the 1 bug,
[20:41] <ikonia> ahh got a few more
[20:42] <tsimpson> I see 54 with the advanced search
[20:42] <ikonia> I see 8 with advanced search
[20:42] <tsimpson> odd
[20:43] <tsimpson> I don't think it's missing any when I search my own bugs, but I don't keep track of all ~570
[20:43] <ikonia> tsimpson: a poor excuse.....
[20:43] <tsimpson> I'm really saying that I have no clue if it's showing all of them or not
[20:44] <ikonia> I know, I'm teasing you, 570 is a lot to track
[20:44] <ikonia> I think I had about 100-ish
[20:44] <ikonia> you see 57, I see 8
[20:46] <ikonia> ah, I get 54 now
[20:48] <ikonia> think it's worth giving this another push ?
[20:48] <ikonia> https://bugs.launchpad.net/ubuntu-cdimage/+bug/307420
[22:54] <AlanBell> meetingology is on its way back into channels
[22:55] <AlanBell> apparently a kline gives it a signal 15 and it dies if I read it correctly
[22:55] <IdleOne> makes sense
[22:56] <IdleOne> you don't want your logs filling up with Unable to connect to server
[23:00] <AlanBell> from the log file "ERROR 2013-07-05T18:54:03 supybot Schedule is the only remaining driver, why do we continue to live?"
[23:01] <AlanBell> eventually life just wasn't worth living it would appear. Poor bot.