Re: [coldsync-hackers] dump conduits fail with 404 Missing Daemon header

[bpaden at trimeros dot com]

Ok, I rebuilt coldsync from CVS and now have no problems.  I still 
don't understand why it wasn't working before, but am unwilling to see 
how far the hole goes :-).

I tried your sample script and had no problems whatsoever, and was
able to get my conduits to behave properly as well.  Maybe I
had a stale file descriptor blocking the write()'s ...? 

Thanks for your quick response and help!

on Wednesday, Apr 07, 2004, Christophe Beauregard, wrote:
> On Tuesday 06 April 2004 16:51, bpaden@trimeros.com wrote:
> > It looks to me like the headers are **never** printed to the conduit,
> > though I have been over and over the code and can't figure out why.
> 
> Okay, I'll bite. I threw together a quick dummy conduit that does all the 
> header magic directly without the ColdSync module (attached). I ran it with 
> the following configuration (using the CVS version, which is largely 
> identical to 3.0-pre4):
> 
> 	conduit fetch,dump {
> 	        type: todo/DATA;
>  	       path: "/home/cpb/src/conduits/non-coldsync";
> 	}
> 
> Both fetch and dump flavours worked flawlessly.
> 
> What are you doing differently?
> 
> c.



-- 
Brett Paden
bpaden@trimeros.com
http://trimeros.com
877.352.data (office)
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.