irc.oftc.net #zumastor log beginning Tue Jul 10 04:12:25 PDT 2007 2007-07-10 10:07 271 messages on lkml since I susbscribed ten hours ago 2007-07-10 10:07 that was the night shift 2007-07-10 10:07 I guess it's 6-700 messages/day now 2007-07-10 12:27 setting up git now 2007-07-10 12:27 whee 2007-07-10 13:37 hi flipz 2007-07-10 13:37 how is your kernel hackery coming along? 2007-07-10 15:20 flips: irc logging was broken for a while so i set it up again last night 2007-07-10 15:20 i gave it a new home 2007-07-10 15:20 http://zumastor.org/irclogs/ 2007-07-10 15:21 before or after I spent the evening bitching about exim4 config? 2007-07-10 15:21 after unfortunately ;) 2007-07-10 15:22 fortunately :) 2007-07-10 15:22 very nice 2007-07-10 15:23 i was thinking of adding a regex to make links show up in the html 2007-07-10 15:24 so that's how you code that kind of page 2007-07-10 15:24 very instructive 2007-07-10 15:24 that would be cool 2007-07-10 15:25 i've used cat $0 before in a photo gallery script generator 2007-07-10 15:25 nice way to make the source available 2007-07-10 15:26 I didn't even notice that 2007-07-10 15:27 hm would it be better of the recent conversation was reversed (most recent first)? 2007-07-10 15:27 i've always wanted to find a use for "tac" 2007-07-10 15:27 ah that displays the script itself on the page with appropriate escaping 2007-07-10 15:28 I prefer it forward 2007-07-10 15:28 ACTION continues his search for a use of tac 2007-07-10 15:28 but the blank line should be at the bottom instead of the top 2007-07-10 15:29 i think thats browser lameness 2007-07-10 15:29 looks much better in opera 2007-07-10 15:30 fair enough 2007-07-10 15:30 it's great as it is 2007-07-10 15:30 ah looks better in konq 2007-07-10 15:31 a new log file gets generated at midnight with a cronjob 2007-07-10 15:31 rotated 2007-07-10 15:31 so the "archives" will have a list of files names 2007-01-01.txt 2007-07-10 15:31 like that 2007-07-10 15:32 perfect 2007-07-10 15:32 will need a search feature though 2007-07-10 15:32 international format dates even 2007-07-10 15:32 oh yes, hmm ht:dig? 2007-07-10 15:32 grep? 2007-07-10 15:32 ht:dig is basically accelerated grep 2007-07-10 15:33 i like to roll my own 2007-07-10 15:33 like to write your own indexing? 2007-07-10 15:34 we'll see when we get enough logs for it to matter 2007-07-10 15:34 taking user input in cgi bash scripts is scary 2007-07-10 15:34 is that your own irc client too? 2007-07-10 15:34 no its linked off the page 2007-07-10 15:34 youd' like it 2007-07-10 15:34 it uses fifos 2007-07-10 15:34 for commands 2007-07-10 15:35 I'll try it 2007-07-10 15:35 even uses the filesystem as a database, where have I seen that before? 2007-07-10 15:35 :) 2007-07-10 15:36 debian doesn't seem to have it 2007-07-10 15:38 10. Is this punk really dddrunken(tm) all the time? Yes. 2007-07-10 16:01 http://episteme.arstechnica.com/eve/forums/a/tpc/f/96509133/m/378003404831 2007-07-10 16:24 -!- erwan_taf(~erwan@216.141.86.3) has joined #zumastor 2007-07-10 19:09 -!- erwan_taf(~erwan@216.141.86.3) has joined #zumastor 2007-07-10 22:42 -!- flipz(~daniel@dsl081-085-152.lax1.dsl.speakeasy.net) has joined #zumastor 2007-07-10 22:46 hi flipz 2007-07-10 22:46 hi shapor 2007-07-10 22:46 so rc1 of util-linux-ng is out and it support libvolume_id (which uses udev) instead of libblkid 2007-07-10 22:46 had a vacuum cleaner power event 2007-07-10 22:47 and it is already going in to debian unstable :) 2007-07-10 22:47 aha, well I guess andreas didn't know 2007-07-10 22:48 well its configurable, --with-fsprobe={blkid,volume_id} and by default its off 2007-07-10 22:48 its the 2nd thing mentioned in the release highlights 2007-07-10 22:48 so after the power event everything came up again ok, exept exim took about 1 minute to start 2007-07-10 22:48 timing out looking up something I think 2007-07-10 22:48 seems like a long time to timeout 2007-07-10 22:50 I wonder if I should set the name of the machine to 127.0.0.1 instead of local ip 2007-07-10 22:51 set the ip I mean 2007-07-10 23:25 that doesn't sound right to me irc.oftc.net #zumastor log beginning Wed Jul 11 00:00:01 PDT 2007 2007-07-11 06:10 -!- erwan_taf(~erwan@216.141.86.3) has joined #zumastor 2007-07-11 09:20 -!- jiayingz(~jiayingz@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-11 10:39 flipz ping 2007-07-11 10:40 hi shapor 2007-07-11 10:56 so i was thinking about the second snapshot downstream 2007-07-11 10:56 one as a reference and one to mount (potentially r/w) 2007-07-11 10:57 there is a problem with the snapshot number name space 2007-07-11 10:58 if we replicate snapshot n to snapshot n downstream, what number do we assign to the one we are going to mount 2007-07-11 10:58 ay other valid snapshot number could be the next incoming snapshot num 2007-07-11 11:01 so keeping the snapshot numbers the same was nice in the beginning but doesn't really work with this scheme 2007-07-11 11:01 which is fine, we can just track the master snapshot number in the database 2007-07-11 11:01 hold.upstream or something 2007-07-11 11:11 i really dont like the snapshot numbers differing, it would following whats happening with chained replication quite painful 2007-07-11 11:26 yes indeed, I guess we hit that issue immediately 2007-07-11 11:27 should we increment snap numbers by two? 2007-07-11 11:40 always or just in the case of a replication snapshot? 2007-07-11 11:42 yeah we could bump the "next" snapnum by two when we take one for repliction, under the assumption downstream will want to take the next number as well 2007-07-11 11:43 then we just have the case that we happen to do 2^32-2 snapshots before we replicate again 2007-07-11 11:44 in which case the snapnums could collide 2007-07-11 11:44 although i guess we dont handle wrapping snapshot nums in zumastor properly anyway 2007-07-11 11:44 we never account for it (oops) 2007-07-11 11:45 this came up when i was explaining how zumastor worked to chris 2007-07-11 11:45 do we even need the master if ddsnap create just picks an available snapshot number for us? 2007-07-11 11:45 er i mean ddsnap server 2007-07-11 11:46 and it returns it 2007-07-11 11:46 that way we do the atomic increment in the ddsnap server 2007-07-11 11:46 and snapshot creation requests are just done by calling ddsnap create rather than writing to the master fifo 2007-07-11 11:47 it could just print out the snapshot number it picked 2007-07-11 13:40 shapor, always, which leaves the odd numbers free for use downstream 2007-07-11 13:40 really simple minded namespace allocation 2007-07-11 13:42 ddsnap can't pick a good snapshot number by itself, it need to avoid colliding with other servers 2007-07-11 13:42 extending snapshot tag to 64 bits would be really easy 2007-07-11 13:42 "let's see you overflow that, buddy" 2007-07-11 13:43 wrapping should be done by the script anyway, it's policy 2007-07-11 13:45 we should actually state that design rule: ddsnap provides mechanism, not policy 2007-07-11 13:46 even zumastor should try to let the admin provide policy, though perhaps not in the case of choosing snapshot numbers 2007-07-11 13:48 -!- cbsmith(~xman@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-11 13:49 now its a party 2007-07-11 13:49 nice 2007-07-11 13:50 ACTION predicts that going to 64-bits just means that when something fork bombs it'll take longer to crash. ;-) 2007-07-11 13:50 can bash even deal with 64 bit ints? hm 2007-07-11 13:52 looks like bash's math is 64 bit signed 2007-07-11 13:52 Ah, so you probably don't want to go past 2^63 then. 2007-07-11 13:53 well something other than bash wilb e doing our snapshot to id mapping eventually 2007-07-11 13:53 once we are supporting arbitrary naming of snapshots 2007-07-11 13:53 a .9 feature i beleive? maybe 1.0 2007-07-11 13:53 How about 0.5 ;-) 2007-07-11 13:55 actually it might be 2007-07-11 13:56 it is 2007-07-11 13:56 hm more bash filesystem database? 2007-07-11 14:16 flipz: the collision issue with other servers isn't really an issue for the master 2007-07-11 14:16 it is the source of all replication 2007-07-11 14:17 what about a flag to ddsnap create that asked for the largest snapshot number plus one 2007-07-11 14:17 then we wouldn't need a master daemon 2007-07-11 14:17 shapor: That seems.... bad. 2007-07-11 14:18 why? 2007-07-11 14:18 shapor: Oh wait, why not just ask ddsnap to give us an ID, and let it worry about the logic? 2007-07-11 14:18 04:08PM we should actually state that design rule: ddsnap provides mechanism, not policy 2007-07-11 14:18 ah. 2007-07-11 14:19 so instead of "ddsnap create /path/sock " 2007-07-11 14:19 "ddsnap create /path/sock --auto" 2007-07-11 14:19 and it returns success and prints out the snap num 2007-07-11 14:20 yeah! 2007-07-11 14:20 that would allow us to lose a fifo 2007-07-11 14:20 and allow "zumastor snapshot" to return an error 2007-07-11 14:20 if there is one 2007-07-11 14:20 rather than having to check the log file 2007-07-11 14:20 So then the only problem is that makes it harder to do the "skip one" trick, right? 2007-07-11 14:20 right 2007-07-11 14:21 so --auto 2 ? 2007-07-11 14:21 heh 2007-07-11 14:21 ACTION smacks shapor 2007-07-11 14:22 How about you just create the snapshot twice and throw one away? That feels perfectly horribly hacky to me. 2007-07-11 14:22 racy 2007-07-11 14:23 if you are replicating to two hosts, or have shceduled snapshots getting created at the same time 2007-07-11 14:23 that was the whole point of the master 2007-07-11 14:23 oh yeah, forget that. 2007-07-11 14:24 I say just make it always skip by 2 for now. 2007-07-11 14:25 ddsnap create {<--next [n]>|} 2007-07-11 14:25 policy and mechanism man.... 2007-07-11 14:25 its not policy 2007-07-11 14:26 ACTION heads to the office 2007-07-11 14:26 ddsnap create --really-bad-hack? ;-) 2007-07-11 14:26 you want to see a really bad hack look at what we do when we mount a snapshot! 2007-07-11 14:26 mount && umount && mount 2007-07-11 14:26 you will have a hard time finding a simpler policy than "odd numbers are local" I think 2007-07-11 14:26 ;) 2007-07-11 14:27 it has a comment I hope? 2007-07-11 14:27 yes 2007-07-11 14:27 i believe 2007-07-11 14:27 # mount ro, umount, and re-mount to work around free blocks bug in ext3 2007-07-11 14:27 flipz: but that wouldn't be the policy if we only skip by 2 some of the time, right? 2007-07-11 14:28 cbsmith: he was saying to always skip one 2007-07-11 14:28 shapor: ah, I see. he was agreeing with me. 2007-07-11 14:28 yeah 2007-07-11 14:29 the issue of adding a --next flag and getting rid of the master is orthogonal 2007-07-11 14:30 --ugly-hack-is-better-than-a-bash-dameon-and-fifo 2007-07-11 14:30 yes 2007-07-11 14:31 how about just "--you-gotta-love-bash" or "--bash-to-know-it-is-to-love-it" 2007-07-11 15:08 so if selecting the next snapshot was the only reason for the master that would be a good hack, but we have manage the snapshot lists for scheduled snapshots as well 2007-07-11 15:11 ddsnap selecting the snapshot number doesn't sound right to me 2007-07-11 15:12 flips: why? 2007-07-11 15:12 smells like policy 2007-07-11 15:12 flips: I guess it is, but the only policy going forward would be that it is unique. 2007-07-11 15:13 flips: And that is probably something useful to enforce in ddsnap yes? 2007-07-11 15:13 flips: who else can tell you if a snapshot number is not in use? 2007-07-11 15:13 I doubt it 2007-07-11 15:13 only ddsnapd knows 2007-07-11 15:13 I don't have my arguments all in a row in the moment, it sounds wrong though 2007-07-11 15:14 ok 2007-07-11 15:14 ok, for one thing, a local ddsnap can't possibly known what snapshot numbers are in use downstream 2007-07-11 15:15 feature, not bug. ;-) Having those two linked is gonna be a problem going forward anyway. 2007-07-11 15:16 your solution is to add another layer of indirection? 2007-07-11 15:17 flips: Either that or to make the numbers largely irrelevant. 2007-07-11 15:17 I say just make it always skip by 2 for now. <- I should just shut up here :) 2007-07-11 15:17 hehe 2007-07-11 15:17 flips: yes 2007-07-11 15:17 that is what i'm going to do 2007-07-11 15:17 this is an orthogonal issue 2007-07-11 15:18 and not one we need to worry about 2007-07-11 15:18 Oh sure. I wasn't talking about righ tnow. 2007-07-11 19:05 .quit 2007-07-11 19:24 sshd was in fact running here 2007-07-11 19:24 now what 2007-07-11 19:25 ah, there was an "enable" box not checked on the router irc.oftc.net #zumastor log beginning Thu Jul 12 00:00:01 PDT 2007 2007-07-12 06:39 -!- erwan_taf(~erwan@216.141.86.3) has joined #zumastor 2007-07-12 14:48 -!- cbsmith(~xman@207.47.98.129.static.nextweb.net) has joined #zumastor irc.oftc.net #zumastor log beginning Wed Jul 13 00:00:01 PDT 2007 2007-07-13 11:24 hi zumalog 2007-07-13 11:27 flipz: I am an intelligent robot 2007-07-13 11:28 so am I, we have much incommon 2007-07-13 11:30 flipz: but I am elegant, only 497 lines of c 2007-07-13 11:31 I am about 4 billion lines of amino acid, considerably less elegant 2007-07-13 11:54 flipz: please review the custom rotation patch i just sent 2007-07-13 11:55 will do 2007-07-13 13:33 shapor, what are the underscores on __manual for? 2007-07-13 13:45 flipz, in case someone calls their custom snapshot rotation manual 2007-07-13 13:45 that seems more likely than __manual 2007-07-13 13:45 because it needs to have a special keyword to give them master when it wants to take a snapshot for no reason 2007-07-13 13:46 i suppose something with a slash in it would be better 2007-07-13 13:46 because we dont allow slashes 2007-07-13 13:46 due to fs database 2007-07-13 14:13 I don't see the name collision right away 2007-07-13 14:58 flipz because the snapshot rotation name is what gets written to the master trigger 2007-07-13 15:31 I still don't see the collision 2007-07-13 15:32 perhaps because I'm only looking at a patch and it's too much work to apply it and see what the whole file looks like 2007-07-13 16:10 "zumastor snapshot " simply writes to the master trigger 2007-07-13 16:11 if you dont specify , it sends "manual" 2007-07-13 16:11 for the master to know to not attempt to do snapshot rotation stuffs 2007-07-13 16:11 i made it /manual now, because /'s aren't allowed in custom snapshot "kinds" 2007-07-13 16:11 due to fs database 2007-07-13 16:12 same for target replication, it writes "target host.com" to the master trigger 2007-07-13 16:12 now changed to "target/host.com" 2007-07-13 16:13 so it wouldn't collide with a custom rotation name of "target host.com", not that anyone is likely to use one 2007-07-13 22:32 -!- juuva(juuva@peili.org) has joined #zumastor irc.oftc.net #zumastor log beginning Sat Jul 14 00:00:01 PDT 2007 2007-07-14 06:02 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor 2007-07-14 14:18 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor 2007-07-14 16:19 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 16:24 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-14 16:34 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 17:05 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 17:14 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 17:20 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-14 17:22 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 17:40 -!- shapor_(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-14 17:40 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 18:07 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 18:22 -!- shapor_(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-14 18:45 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 18:49 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-14 20:25 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 21:28 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-14 21:28 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor irc.oftc.net #zumastor log beginning Sun Jul 15 00:01:53 PDT 2007 2007-07-15 01:04 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-15 03:17 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-15 14:02 -!- murble(~murbix@soapstone.yuri.org.uk) has joined #zumastor 2007-07-15 14:04 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor irc.oftc.net #zumastor log beginning Mon Jul 16 00:00:01 PDT 2007 2007-07-16 01:21 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-16 12:00 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor irc.oftc.net #zumastor log beginning Tue Jul 17 00:00:01 PDT 2007 2007-07-17 13:07 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor irc.oftc.net #zumastor log beginning Wed Jul 18 00:00:01 PDT 2007 2007-07-18 02:00 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-18 04:09 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-18 08:55 -!- jdries3(~jdries3@72.14.228.89) has joined #zumastor irc.oftc.net #zumastor log beginning Thu Jul 19 00:00:01 PDT 2007 2007-07-19 07:32 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-19 07:37 -!- jdries3(~jdries3@72.14.224.1) has joined #zumastor 2007-07-19 08:09 -!- jdries3(~jdries3@c-69-249-52-124.hsd1.nj.comcast.net) has joined #zumastor 2007-07-19 08:10 -!- jdries3_(~jdries3@72.14.224.1) has joined #zumastor 2007-07-19 09:43 -!- phlyps(~daniel@dsl081-085-152.lax1.dsl.speakeasy.net) has joined #zumastor 2007-07-19 10:19 -!- cbsmith(~xman@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-19 11:57 -!- jdries3(~jdries3@72.14.224.1) has joined #zumastor 2007-07-19 12:09 -!- jdries3_(~jdries3@72.14.224.1) has joined #zumastor 2007-07-19 12:17 -!- jdries3(~jdries3@72.14.224.1) has joined #zumastor 2007-07-19 12:43 -!- jdries3_(~jdries3@72.14.224.1) has joined #zumastor 2007-07-19 19:13 -!- jdries3(~jdries3@c-69-249-52-124.hsd1.nj.comcast.net) has joined #zumastor irc.oftc.net #zumastor log beginning Fri Jul 20 00:00:01 PDT 2007 2007-07-20 02:05 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-20 11:14 http://news.com.com/8301-10784_3-9747716-7.html?tag=recentPosts 2007-07-20 12:05 cbsmith, exciting times 2007-07-20 12:28 phlyps: no kidding 2007-07-20 15:46 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-20 15:46 -!- cbsmith(~xman@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-20 15:46 -!- phlyps(~daniel@dsl081-085-152.lax1.dsl.speakeasy.net) has joined #zumastor 2007-07-20 15:46 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-20 15:46 -!- juuva(juuva@peili.org) has joined #zumastor 2007-07-20 15:46 -!- jiayingz(~jiayingz@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-20 15:46 -!- fmayhar(~fmayhar@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-20 15:46 -!- flips(~phillips@207.47.98.129.static.nextweb.net) has joined #zumastor irc.oftc.net #zumastor log beginning Sat Jul 21 00:00:01 PDT 2007 irc.oftc.net #zumastor log beginning Sun Jul 22 00:00:01 PDT 2007 2007-07-22 03:30 -!- tleuser(~tleuser@125-26-234-22.adsl.totbb.net) has joined #zumastor 2007-07-22 12:59 -!- phlyps(~daniel@dsl081-085-152.lax1.dsl.speakeasy.net) has joined #zumastor 2007-07-22 12:59 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-22 12:59 -!- jiayingz(~jiayingz@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-22 12:59 -!- fmayhar(~fmayhar@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-22 12:59 -!- flips(~phillips@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-22 13:01 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-22 13:01 -!- juuva(juuva@peili.org) has joined #zumastor irc.oftc.net #zumastor log beginning Mon Jul 23 00:00:01 PDT 2007 2007-07-23 08:26 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor 2007-07-23 09:35 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor irc.oftc.net #zumastor log beginning Tue Jul 24 00:00:01 PDT 2007 2007-07-24 05:28 -!- erwan_taf(~erwan@LAubervilliers-151-13-63-69.w217-128.abo.wanadoo.fr) has joined #zumastor 2007-07-24 11:37 -!- murb(~murbix@soapstone.yuri.org.uk) has joined #zumastor 2007-07-24 11:47 sigh, another hole in bind 2007-07-24 11:55 seams that it's time for upgrade 2007-07-24 11:59 who uses bind for a caching server anyway? 2007-07-24 11:59 dnscache is far better 2007-07-24 12:01 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor irc.oftc.net #zumastor log beginning Wed Jul 25 00:00:01 PDT 2007 2007-07-25 01:11 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-25 17:57 -!- fmayhar(~fmayhar@207.47.98.129.static.nextweb.net) has joined #zumastor irc.oftc.net #zumastor log beginning Thu Jul 26 00:00:01 PDT 2007 2007-07-26 02:00 -!- flipz(~daniel@dsl081-085-152.lax1.dsl.speakeasy.net) has joined #zumastor 2007-07-26 02:00 -!- jiayingz(~jiayingz@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-26 02:00 -!- fmayhar(~fmayhar@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-26 02:00 -!- juuva(juuva@peili.org) has joined #zumastor 2007-07-26 02:00 -!- murb(~murbix@soapstone.yuri.org.uk) has joined #zumastor 2007-07-26 02:00 -!- erwan_taf(~erwan@81.80.43.67) has joined #zumastor 2007-07-26 02:00 -!- shapor(~shapor@yzf.shaptech.com) has joined #zumastor 2007-07-26 14:47 -!- flips(~phillips@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-26 14:49 shapor, ping? 2007-07-26 22:24 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor irc.oftc.net #zumastor log beginning Fri Jul 27 00:00:01 PDT 2007 2007-07-27 12:56 jiayingz, there? 2007-07-27 13:27 hi flipz irc.oftc.net #zumastor log beginning Sat Jul 28 00:00:01 PDT 2007 2007-07-28 01:12 -!- zumalog(~zumalog@yzf.shaptech.com) has joined #zumastor irc.oftc.net #zumastor log beginning Sun Jul 29 00:00:01 PDT 2007 2007-07-29 21:10 -!- juuva(juuva@peili.org) has joined #zumastor irc.oftc.net #zumastor log beginning Mon Jul 30 00:00:01 PDT 2007 2007-07-30 10:24 -!- cbsmith(~xman@207.47.98.129.static.nextweb.net) has joined #zumastor 2007-07-30 11:29 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor irc.oftc.net #zumastor log beginning Tue Jul 31 00:00:01 PDT 2007 2007-07-31 00:07 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor 2007-07-31 00:07 -!- juuva(juuva@peili.org) has joined #zumastor 2007-07-31 09:38 good morning 2007-07-31 09:39 evening 2007-07-31 10:41 ACTION is busy saving the linux world from the dread memory recursion bogeyman 2007-07-31 10:42 hmm, I really ought to blog about this one 2007-07-31 10:42 what is a decent blogging package? 2007-07-31 12:36 I have broken my exim4 configuration again, it won't relay localhost 2007-07-31 12:37 perhaps because I haven't told it explicitly to relay for the machine domain name, but just for localhost 2007-07-31 12:38 which works so long as I make the /etc/hosts entry for the machine name 127.0.0.1, but that is broken for other reasons 2007-07-31 12:38 I suppose I need to go dive into exim4.conf.conf once again :-( 2007-07-31 13:17 -!- jinevill(~justin@74.94.201.89) has joined #zumastor 2007-07-31 13:55 hi flipz 2007-07-31 13:56 i thought you fixed that issue 2007-07-31 13:56 getting ready to post to lkml? 2007-07-31 14:07 shapor, I fixed it by entering 127.0.0.1 moonbase into /etc/hosts, but that is not a nice fix 2007-07-31 14:07 so I have changed that back to the proper hosts entry, and now local relaying goes back to being broken 2007-07-31 14:08 I think I would prefer to learn the issue before just starting over again with postfix 2007-07-31 14:09 I suspect I would hit much the same issues with postfix, i.e., stupidly complex config file, relaying disabled in more than one place, the purpose and format of essential files undocumented or poorly documented in some nonobvious place 2007-07-31 14:15 you should have a pretty simple case, you'd think there'd be a howto on setting exim out there 2007-07-31 14:16 decent blogging package.. hmm, vi? ;) 2007-07-31 14:17 grey matter and nucleus are looking pretty good 2007-07-31 14:18 blogging with vi -> html ranks right up there with blogging by standing on 3rd street and shouting out my thoughts ;) 2007-07-31 14:18 good idea! 2007-07-31 14:19 ACTION is heading to the office 2007-07-31 14:26 -!- erwan_taf(~erwan@konilope.linuxeries.org) has joined #zumastor 2007-07-31 14:26 -!- juuva(juuva@peili.org) has joined #zumastor 2007-07-31 16:15 -!- jinevill(~justin@12.126.68.218) has joined #zumastor