-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Mar 08, 2004 at 11:24:48AM -0500, Adam Back wrote: >OK, now I figured out what the grep( /^--$/ .. 0, @args ) idiom means, >I found the fix: > >replace the 0 with undef: > >grep( /^--$/ .. undef, @args ) > >I suppose it could be perl version specific problem even. I have >5.8.3 on fedora-core1. I can only suppose that as /^--$/ is matching >a string that the 2nd arg is also converted to a string and "0" is >probably true as a string (in some versions of perl)?? Aha! I wondered if it was a Perl version thing. I'll fix this, thanks! >Perhaps another way to do this would be an argument to >hashcash-sendmail which could cause it to start a daemon. (It could >for example keep track using a file with the process id, which is >removed by hashcash-daemon when it receives kill signal). What I'm thinking is to have the daemon write its PID to a file in the work directory. Then hashcash-sendmail can check whether there's one running that way. That has a couple of problems, and I haven't done it yet. I'm wondering if there's a better way...something that'll make it all "just work." >btw you might want a lower default? I've put ^:20:19 in >.hashcash/bitconf. 26 bits is a fair bit of grunt on a multi-user >system where you are not root. What do you suggest? I'm basically taking my cue from SpamAssassin, which recognizes 26 bits as being worth a -5 to the spam score. - -- Kyle Hasselbacher | First Church of Springfield kyle@xxxxxxxxxxx | God welcomes His victims. -- "The Simpsons" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFATKaV10sofiqUxIQRAjGxAKDteRgSD8RrjtDAI+e51CuDRos7cwCglc1n Q3rfbcGDTZUh8OEf1S6sG3g= =2nlp -----END PGP SIGNATURE-----