18:14:30 #startmeeting 18:14:30 alpo: ok 18:14:30 Meeting started Tue Oct 4 18:14:30 2011 UTC. The chair is coxn. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:14:32 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:14:37 because we sometimes want to make shell accounts and membership at different times 18:14:40 coxn: thanks! 18:14:40 #chair alpo 18:14:41 Current chairs: alpo coxn 18:14:46 #chair justis 18:14:47 Current chairs: alpo coxn justis 18:14:53 #chair billf 18:14:53 Current chairs: alpo billf coxn justis 18:14:57 #chair snyrk 18:14:57 Current chairs: alpo billf coxn justis snyrk 18:14:59 does the shell account name get recorded in the member db ? 18:15:13 billf: i don't believe so 18:15:25 i think you'd have to reference it in the other direction from ldap 18:15:32 gents, I'm in the middle of building about 8 machines 18:15:37 I don't want to bail on the meeting though 18:15:48 if you need my attention/feedback, please ping me 18:15:51 coxn: well, that's all automated, right? =) 18:16:49 cool beans. worst case scenario I'll review the logs/minutes later 18:16:59 tty soonish 18:17:00 If someone wanted to help with processing the forms, we could work a night to come over to my place 18:17:05 * coxn returns to building 18:17:05 * alpo just printed a handful of blank membership forms 18:17:37 where do the processed forms go ? 18:17:50 (trash) 18:17:51 away 18:18:13 really, the process is quick 18:18:23 alpo: no, it's slow and error prone 18:18:46 Tool Wars #17: Alpo v Snyrk: Membership Forms 18:19:28 I abstain from commenting until I have performed the proceedure 18:20:19 billf: happy to help, but i'm unavailable for ~2 weeks 18:21:12 i'll look into a web form when i'm visiting VA 18:21:35 on that note, i will miss this month's meeting 18:21:47 billf: FB event is created and all the members of the FB group have been invited 18:21:57 snyrk: awww 18:22:02 justis: thanks 18:22:35 justis: yeah, bummed... i'll miss you guys... *sniff* 18:22:54 snyrk: and a good meeting 18:23:07 is Drew prepared to give his talk, given that we haven't got anything from him yet ? 18:24:31 should we have an "emergancy talk" prepared for this and future meetings ? 18:24:47 my "emergency talk" was RAID-LVM 18:25:03 i could give it again :-) 18:25:16 you could do a talk on LVM-RAID 18:27:46 billf: to the more general question, yes, we should have a backup plan for every meeting 18:28:17 ok, and to the first, is Drew good to go ? 18:28:30 billf: not sure on that one 18:29:07 calling drew now 18:29:48 went to voicemail 18:29:52 moving to email 18:34:20 email to Drew sent 18:34:46 @topic Who's ordering pizza for Oct 13? 18:34:47 justis: (topic []) -- Returns the topic for . is only necessary if the message isn't sent in the channel itself. 18:34:54 #topic Who's ordering pizza for Oct 13? 18:36:34 * alpo is not opposed to ordering 18:36:36 i will not be in town, but available by phone if anything goes wrong 18:37:45 alpo: Can I consider this delegated to you until you talk coxn into doing it? 18:38:25 fine 18:38:31 i'll put it on my calendar 18:38:55 alpo: thanks :) 18:39:44 #topic status of systems 18:40:05 is there anything we need to consider about our servers before the next meeting? 18:40:13 I'm hoping it can all wait 18:40:17 but want to give a chance to cover it 18:40:45 pilot still has a pending pvmove, right ? 18:40:51 my only thought is that with dargo offline/being reinstalled, we have lost our backuppc machine 18:41:09 #action alpo to order pizza 18:41:14 we should "pvmove --abort" 18:41:25 i did a quick sync of /root to rygel a week or so back 18:41:40 snyrk: good point 18:41:44 err... "/" 18:41:49 alpo: that sounds like a good idea 18:42:13 does anyone see any reason why i should not do the pvmove --abort now-ish ? 18:42:42 that's not a command i use regularly enough to know the possible issues 18:42:59 that said, i'm not interested in recovering another RAID5 array anytime soon 18:43:14 i bet :-) 18:43:41 alpo: my reaction is the same as snyrk 18:43:45 was it the pmove that caused the problem ? 18:44:06 it caused the I/O to block last saturday, yes 18:44:26 pvmove --abort will tell it to forget about any pending pvmove that it was doing 18:45:13 that is, anything that has been moved is OK, but it clears the queue of other stuff to be moved later 18:48:15 alpo: I agree. Do a "pvmove --abort" 18:48:53 any other pressing issues to discuss about systems? 18:50:15 #topic meeting wrap-up 18:50:26 anything else to discuss before we dismiss? 18:51:01 coxn alpo snyrk billf ... ? 18:51:52 err... kernel update? 18:51:53 i have no critical business 18:51:57 which can wait 18:52:01 until we have a plan 18:52:15 so... motion to adjourn 18:52:58 when is Peak10's next party >? 18:53:26 billf: :D 18:53:38 hopefully, their next party is on a day I can actually attend 18:53:43 sounds like I missed a good time 18:54:17 #action snyrk to draft placeholder text for announcing November meeting *prior to next SC meeting* 18:54:29 #action billf to process new member applications 18:54:37 #action alpo to pvmove --abort 18:54:57 coxn: cool ... thanks for the help and good luck with your builds 18:55:16 billf: thanks for your help and input ... I hope your day goes well :) 18:55:24 #action billf to get some more sleep 18:55:44 alpo: thanks for untangling the pvmove and for getting pizza 18:56:05 snyrk: thanks for your contributions ... have fun in VA :) 18:56:14 back to freak'n windows device drivers 18:56:18 #topic meeting adjourned 18:56:27 billf: lol, sympathies 18:57:23 justis: very welcome, glad to know things are in such good hands 18:58:33 #save 18:59:08 #endmeeting