[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Re: Coldsync 2.2.5 daemon available for download
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Re: Coldsync 2.2.5 daemon available for download
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Sat, 02 Nov 2002 23:42:35 +0100
- In-Reply-To: <20021102.2Tn.15016700@axis.terralab.com>
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On 02-Nov-02 at 19:33:11,
Adam Hull <adam@terralab.com> wrote:
> I was under the impression that colsync was being made to work with inetd
> and not as a daemon. So, I thought it would be helpful to provide a way
> for those who are interested in using coldsync as a daemon to get up and
> running quickly. And I personally need to base my work on stable releases.
> So, I am stuck using 2.2.5 for the time being.
Yes, we decided to develop coldsync as an inetd daemon and not as
a standalone daemon because we thought it was a more stable
solution for a 24x7 use.
The only thing that prevented coldsync 2.2.5 to work with inetd was
a missing if()statement and not a protocol one. yes, maybe the lack
of documentation too...
I think coldsync will be declared stable in a few weeks, if this makes any sense...
on the contrary, coldsync 2.2.5, has a lot of bugs in other parts of the
code.
the cvs version has a lot of cool new features like more headers available
to conduits, an improved SPC.pm, a VFS.pm, support for auto-initialization of devices,
faster download of dbs list and a better error reporting.
--
- 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.