[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Re: Real life experiences with netsync
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Re: Real life experiences with netsync
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Tue, 05 Nov 2002 08:00:52 +0100
- In-Reply-To: <NEBBJEJDOJKNMNOFCBEAGEHJENAA.robb@empire2.com>
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On 05-Nov-02 at 02:19:56,
Rob Bloodgood <robb@empire2.com> wrote:
> list),
> here is my patch against 2.2.5 which provides homedir support for a single
> coldsync user.
thank you.
> ... and now that I look at it, it seems to be integrated with a patch to
> add UserID and UserName headers to the conduit header list. I know there
> has been effort in the realm of expanding the headerlist conduits receive
> anyway, so I'm not going to worry about supplying code for it... it's
> likely so ancient as to be embarrassing at this point.
> (but I'll post if asked :-)
;-) There's a similar funcionality in the current code. You can use the
dump-headers conduit to see the new headers. If you need mor,e
just ask ;)
> line 650. I would contribute further but there is the config mechanism
> which I don't know to account for. It would make more sense as a
> .coldsyncrc option than as a commandline switch, altho it might go both
> places. You know better than I.
better a .coldsyncrc option...
there are already too many cmd line switches.
It would be fine if the user can provide a string like "/home/coldsync/%u"
or "/home/%u" in the config file.
--
- alex.
--
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.