[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] autorescue
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] autorescue
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Thu, 18 Apr 2002 22:47:55 +0100
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
I'm going to implement the autorescue option.
Here are my thoughts.. if someone has suggestions, critics or
anything else, feel free to send an email.
A new directory will be created: ~/.palm/rescue . When hotsyncing
in daemon mode, coldsync will check if userid == 0. If true,
any file in /rescue will be copied to /install.
If autoinit is also enabled, it will be executed before autorescue.
This approach allow us to obtain the rescue functionality
without changing too much code in coldsync. Moreover,
any db in /install will get a chance to have it's install conduit
run after the upload.
This will obviously work only if the autoinit feature is enabled
and worked correctly, since coldsync need to have an exact
match on the username to find the right rescue directory.
An option would be to have a global, site-wide, rescue directory
(/var/lib/coldsync/rescue ?) whose content will
be installed early in the coldsync process. However,
install conduits will not be run on those files.
--
- alex.
P.S. Should this feature be also active in normal sync mode?
If yes, should files in /var/lib/coldsync/rescue uploaded as well?
--
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.