opensync-users — The place to get help for the OpenSync project

Re: [Opensync-users] syncml-obex-client hanging..

[Anton Y. <yak...@gm...>]

Hi again,

Does anyone has any ideas?
I'm quite confused(

2008/1/9, Anton Yakimov <yak...@gm...>:
>
> Hello,
>
> Unfortunatly syncml-obex plugin freezes and doesn't continue..
>
> Here is msynctool log:
> kekc@KeKc:~/.opensync/group1/2$ msynctool --sync "Nokia 6021"
> Synchronizing group "Nokia 6021"
> Member 1 of type kdepim-sync just connected
> <freeze here>
>
> And syncml-obex-client log:
> kekc@KeKc:~$ syncml-obex-client --sync text/x-vcalendar Calendar -b
> 00:14:A7:57:BC:06 11 --identifier "PC Suite" --version " 1.1" --wbxml
> --useStringTable
> connection with device succeeded
> <freeze here>
>
> Opensync version is 0.22. Distributive - Ubuntu 7.10.
> Mobile phone - Nokia 6021. I saw opensync device compability list and it's
> OK with it, s I'm quite confused((
>
> Please help me!
> Thanks in advance!
>
>

Re: [Opensync-users] two basic (FAQ) questions by noob

[David B. <br...@un...>]

>>>>> "Juha" == Juha Tuomala <Juh...@ik...> writes:


    Juha> I guess rsync is more inclined to machine-to-machine content
    Juha> transfers (like ftp mirroring) and unison more human
    Juha> initated (home dir files etc).

And if both directories are on the same machine, or you can make the
appear so, there are a variety of merging tools like kdiff3, xxdiff,
fhist, imediff2, meld, and dirdiff (to quote a few options on Debian),
that may be better for particular applications.  I have personally
been happy enough with kdiff3 for casual use.  

David

Re: [Opensync-users] two basic (FAQ) questions by noob

[Juha T. <Juh...@ik...>]

On Sunday 13 January 2008 02:03:26 Jerzy Jalocha N wrote:
> Daniel, thank you very much for your quick answer. You provided so
> much more information than I ever expected! I see that OpenSync is not
> the tool for my task, right now, and I will dig deeper into rsync. I
> will also have a special look at unison, which was completely unknown
> to me.

rsync and unison differ mostly that unison does two-way sync
and rsync only one direction at time.

unison also has a gui, but it's not made with popular desktop
toolkits which I would personally like to see happen some day.

I guess rsync is more inclined to machine-to-machine content 
transfers (like ftp mirroring) and unison more human 
initated (home dir files etc).

Br,

Tuju

-- 
Varo hattupäisiä autoilijoita.

Re: [Opensync-users] Nokia 6300 produces obex errors 68, 64

[Jens <jen...@gm...>]

Am Sonntag, 13. Januar 2008 00:11 schrieben Sie:
> Hi Jens,
>
> I have been syncing my 6300 over bluetooth for a week now, and am very
> happy with the results.  On cursory inspection, my config is the same as
> yours.  The only issue I have encountered so far is the duplication of
> items - I think this only occurred after using Nokia PC suite, however
> this is not a problem for me, because opensync will be my only sync tool
>
> >from now on (actually I use syncevolution to keep evolution in sync with
>
> the free scheduleworld server, and I am also very happy with this too).
>
> Cheers,
>
> Jason.
>
>
Hi Jason
ok I haven=B4t read the complete thread. I =B4m not using PC Suite with Win=
dows.=20
At the first syncronisation i have had also  duplications. in my case it wa=
s=20
the wrong  time zone on my mobilphone.
best wishes Jens

Re: [Opensync-users] two basic (FAQ) questions by noob

[Jerzy J. N <jja...@gm...>]

Daniel, thank you very much for your quick answer. You provided so
much more information than I ever expected! I see that OpenSync is not
the tool for my task, right now, and I will dig deeper into rsync. I
will also have a special look at unison, which was completely unknown
to me.
I felt free to add your excellent answers to the FAQ.
best regards,

Jerzy

Re: [Opensync-users] Nokia 6300 produces obex errors 68, 64

[Jason G. <exp...@lo...>]

Hi Jens,

I have been syncing my 6300 over bluetooth for a week now, and am very
happy with the results.  On cursory inspection, my config is the same as
yours.  The only issue I have encountered so far is the duplication of
items - I think this only occurred after using Nokia PC suite, however
this is not a problem for me, because opensync will be my only sync tool
from now on (actually I use syncevolution to keep evolution in sync with
the free scheduleworld server, and I am also very happy with this too).

Cheers,

Jason.

On Sat, 2008-01-12 at 21:45 +0100, Jens Hüsing wrote:
> Am Sonntag, 6. Januar 2008 02:41 schrieb Jason Grant:
> 
> Dear Jason i am using Nokia 6300 with bluetooth. at opensuse 10.2.
> 
> This is my config for mysynctool and kitchtensync for kde
> 
> libsyncml is 0.4.2-9 and mysynctool is 0.20-7.
> 
> Next week i can try it with evolution, but i have read its working-
> 
> <config>
> 
> <username></username>
> 
> <password></password>
> 
> <type>2</type>
> 
> <bluetooth_address>00:1e:a4:11:15:88</bluetooth_address>
> 
> <bluetooth_channel>11</bluetooth_channel>
> 
> <interface>0</interface>
> 
> <identifier>PC Suite</identifier>
> 
> <version>1</version>
> 
> <onlyLocaltime>1</onlyLocaltime>
> 
> <wbxml>1</wbxml>
> 
> <recvLimit>0</recvLimit>
> 
> <maxObjSize>0</maxObjSize>
> 
> <usestringtable>1</usestringtable>
> 
> <onlyreplace>0</onlyreplace>
> 
> <contact_db>contacts</contact_db>
> 
> <calendar_db>calendar</calendar_db>
> 
> <note_db>notes</note_db>
> 
> </config>
> 
> and its works,
> 
> is your computer and your mobilphone clear?
> 
> Best wishes Jens
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________ Opensync-users mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/opensync-users

Re: [Opensync-users] two basic (FAQ) questions by noob

[Daniel G. <dg...@su...>]

On Saturday 12 January 2008 19:38:48 Jerzy Jalocha N wrote:
> * Opensync looks like a relatively young project to me. (Your latest
> release is labeled 0.35). How stable and SECURE is it? Is it
> recommended for a production environment already, or do you regard it
> more as a product under development?
Secure or safe?

As long as you don't run it as administrator/root it's quite secure ;)

Stable or safe? No, not yet...

Some simple setups are known to work quite well - some quite experimental and 
unstable.

Currently we recommend everyone to make backups of everything for getting in 
touch with OpenSync.

I would say that OpenSync is currently in Alpha state...

>
> * What I am really looking for, is a tool for synchronizing
> directories over the network. Your File-Sync Plugin seems to do
> exactly that, but the FAQ entry is really very limited. It would be
> nice, if you could describe more about it's uses, features, actual
> development status, and specially how it relates/compares with other
> solutions like rsync.

At the moment OpenSync is actually lacking in synchronization of _huge_ files 
and it's not yet possible to synchronize several instances of OpenSync which 
each other...

The strength of OpenSync is currently of syncing tiny data in different 
formats. (PIM data is the best example ...). And this only in the role 
as "Server", the "Client" role is missing. It's the most requested feature... 
and will be there... but not before 0.40.

For syncing filesystems i guess rsync is still the best choice. Or if you're 
looking for something more userfriendly you might check unison (iirc). Maybe 
in the future we can make the Synchronization framework more generic and 
solve the problem to synchronize _huge_ data.

Right now OpenSync has to read everything in memory at once. If you would 
synchronize a DVD ISO with 9GB, you'll need at least 9GB * N. N would stand 
for the number of member which are involved in syncing. This "limitation" 
comes from the OpenSync Synchronization Engine, which is currently hardcoded 
to act as "Server" and read all changes in memory, (convert them if needed), 
compare the changes, map the changed entries, do conflict resolution (if 
any), and commit changes to the other parties/members.

This currently fits perfectly the needs of common PIM Synchronization 
protocols, which are designed to do only "Slow Syncing". It's basically a 
very simple way to synchronize which consists of:
- (fast) syncing, which only transfer the latest changes (since last sync)
- slow syncing, which transfer everything (needed if last sync failed, or 
party got synced in meanwhile with another party - to stay in sync)

OpenSync 0.3x is currently our development branch to introduce some more 
feature like different capabilities. Which is (again) more content/format 
related stuff ... and without any use for plain file syncing.

With the release of OpenSync 0.40 we should think about to get rid of those 
described limitation about...

>
> We noobs out there, searching for solutions to our problems, often
> have a hard time choosing the right tools. And I am under the
> impression, that many times interesting new tools and projects are
> overlooked because of lacking information or documentation.

I see this problem as well. Our development ressource are very limited 
currently... so sorry about the lacking information and the still early alpha 
stage of this code.

best regards,
Daniel

Re: [Opensync-users] Nokia 6300 produces obex errors 68, 64

[Jens <jen...@gm...>]

Am Sonntag, 6. Januar 2008 02:41 schrieb Jason Grant:
Dear Jason i am using Nokia 6300 with bluetooth. at opensuse 10.2.
This is my config for mysynctool and kitchtensync for kde
libsyncml is 0.4.2-9 and mysynctool is 0.20-7.
Next week i can try it with evolution, but i have read  its working-

<config>
<username></username>
<password></password>
<type>2</type>
<bluetooth_address>00:1e:a4:11:15:88</bluetooth_address>
<bluetooth_channel>11</bluetooth_channel>
<interface>0</interface>
<identifier>PC Suite</identifier>
<version>1</version>
<onlyLocaltime>1</onlyLocaltime>
<wbxml>1</wbxml>
<recvLimit>0</recvLimit>
<maxObjSize>0</maxObjSize>
<usestringtable>1</usestringtable>
<onlyreplace>0</onlyreplace>
<contact_db>contacts</contact_db>
<calendar_db>calendar</calendar_db>
<note_db>notes</note_db>
</config>
and its works,
 is your computer and your mobilphone clear?
Best wishes Jens

[Opensync-users] two basic (FAQ) questions by noob

[Jerzy J. N <jja...@gm...>]

Hi, I just discovered opensync by chance, and it looks very
interesting. Two questions I couldn't find satisfactory answers, and
might deserve more extended answers in your FAQ:

* Opensync looks like a relatively young project to me. (Your latest
release is labeled 0.35). How stable and SECURE is it? Is it
recommended for a production environment already, or do you regard it
more as a product under development?

* What I am really looking for, is a tool for synchronizing
directories over the network. Your File-Sync Plugin seems to do
exactly that, but the FAQ entry is really very limited. It would be
nice, if you could describe more about it's uses, features, actual
development status, and specially how it relates/compares with other
solutions like rsync.

We noobs out there, searching for solutions to our problems, often
have a hard time choosing the right tools. And I am under the
impression, that many times interesting new tools and projects are
overlooked because of lacking information or documentation.

Thank you for your beautiful work!

--Jerzy

Re: [Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

I am making some progress with LD_PRELOAD.

test@test:~% msynctool --discover test 2
ERROR: Object Fomrat "" of a database not set

I am using the default configuration for syncml-http-server.



On Jan 9, 2008 10:57 AM, Daniel Gollub <dg...@su...> wrote:
> On Mittwoch 09 Januar 2008, Anil wrote:
> > The file plugin works, but not the syncml plugin.
> > Also, if I set the trace environment variables as suggested on some of
> > the site, it cores even more. Apparently, it has problems getting from
> > the environment:
> >
> >
> > vds5@vds5:~% export OSYNC_TRACE=~
> > vds5@vds5:~% export SYNCML_TRACE=~
>
> Oh, you had _TRACE files enabled?
>
> Unfortunately, a lot of code of our codebase is lacking in one very
> fundamental issue, at least i wasn't aware of it. We have lot's of debugging
> output which includes char pointers which might be NULL. This is wrong, and
> make a lot of pain on Solaris, since libc of Solaris will dereferences this
> NULL pointer (and cause the crash). I wasn't aware of this issue, since i
> only got i touch so far with glibc, anyway it's just bad coding of me and
> just wrong. I'll try to clean this mess up the next days... sorry about that.
> Could you try in meanwhile to preload /usr/lib/0@0.so.1
>
> Jijun Yu, applied  once a big patch which fixed several places in OpenSync
> where those debug output might contain a NULL char pointer.. i reverted it,
> for three reason: i had no idea, i'm just dumb and last but not least i
> wanted to have clean solution instead of tons of mini-ifs in every debug
> statement. I thought about a customized xprintf function (sqlite is using for
> debugging output also an customized one which is portable), or just remove
> unneeded/obsolete debug statements which might include NULL char pointer.
>
> If you're interested what this is all about you might check:
> http://technopark02.blogspot.com/2006/04/solaris-null-pointer-bugs-usrlib00so1.html
>
> best regards,
> Daniel
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>

Re: [Opensync-users] msynctool discover cores

[Daniel G. <dg...@su...>]

On Mittwoch 09 Januar 2008, Anil wrote:
> The file plugin works, but not the syncml plugin.
> Also, if I set the trace environment variables as suggested on some of
> the site, it cores even more. Apparently, it has problems getting from
> the environment:
>
>
> vds5@vds5:~% export OSYNC_TRACE=~
> vds5@vds5:~% export SYNCML_TRACE=~

Oh, you had _TRACE files enabled?

Unfortunately, a lot of code of our codebase is lacking in one very 
fundamental issue, at least i wasn't aware of it. We have lot's of debugging 
output which includes char pointers which might be NULL. This is wrong, and 
make a lot of pain on Solaris, since libc of Solaris will dereferences this 
NULL pointer (and cause the crash). I wasn't aware of this issue, since i 
only got i touch so far with glibc, anyway it's just bad coding of me and 
just wrong. I'll try to clean this mess up the next days... sorry about that. 
Could you try in meanwhile to preload /usr/lib/0@0.so.1

Jijun Yu, applied  once a big patch which fixed several places in OpenSync 
where those debug output might contain a NULL char pointer.. i reverted it, 
for three reason: i had no idea, i'm just dumb and last but not least i 
wanted to have clean solution instead of tons of mini-ifs in every debug 
statement. I thought about a customized xprintf function (sqlite is using for 
debugging output also an customized one which is portable), or just remove 
unneeded/obsolete debug statements which might include NULL char pointer.

If you're interested what this is all about you might check:
http://technopark02.blogspot.com/2006/04/solaris-null-pointer-bugs-usrlib00so1.html

best regards,
Daniel

[Opensync-users] syncml-obex-client hanging..

[KeKc <kek...@gm...>]

Hello,

Unfortunatly syncml-obex plugin freezes and doesn't continue..

Here is msynctool log:
kekc@KeKc:~/.opensync/group1/2$ msynctool --sync "Nokia 6021"
Synchronizing group "Nokia 6021"
Member 1 of type kdepim-sync just connected
<freeze here>

And syncml-obex-client log:
kekc@KeKc:~$ syncml-obex-client --sync text/x-vcalendar Calendar -b
00:14:A7:57:BC:06 11 --identifier "PC Suite" --version " 1.1" --wbxml
--useStringTable
connection with device succeeded
<freeze here>

Opensync version is 0.22. Distributive - Ubuntu 7.10.
Mobile phone - Nokia 6021. I saw opensync device compability list and it's
OK with it, s I'm quite confused((

Please help me!
Thanks in advance!
-- 
View this message in context: http://www.nabble.com/syncml-obex-client-hanging..-tp14716106p14716106.html
Sent from the Opensync - User mailing list archive at Nabble.com.

[Opensync-users] syncml-obex-client hanging..

[Anton Y. <yak...@gm...>]

Hello,

Unfortunatly syncml-obex plugin freezes and doesn't continue..

Here is msynctool log:
kekc@KeKc:~/.opensync/group1/2$ msynctool --sync "Nokia 6021"
Synchronizing group "Nokia 6021"
Member 1 of type kdepim-sync just connected
<freeze here>

And syncml-obex-client log:
kekc@KeKc:~$ syncml-obex-client --sync text/x-vcalendar Calendar -b
00:14:A7:57:BC:06 11 --identifier "PC Suite" --version "1.1" --wbxml
--useStringTable
connection with device succeeded
<freeze here>

Opensync version is 0.22. Distributive - Ubuntu 7.10.
Mobile phone - Nokia 6021. I saw opensync device compability list and it's
OK with it, s I'm quite confused((

Please help me!
Thanks in advance!

Re: [Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

http://pastebin.com/m64e40dbe

The file plugin works, but not the syncml plugin.
Also, if I set the trace environment variables as suggested on some of
the site, it cores even more. Apparently, it has problems getting from
the environment:


vds5@vds5:~% export OSYNC_TRACE=~
vds5@vds5:~% export SYNCML_TRACE=~

vds5@vds5:~% msynctool --discover bb 1
Segmentation Fault (core dumped)
vds5@vds5:~% cat Thread1-29330.log
[1199894110.586501]     >>>>>>>  main(4, 8047d90)
[1199894110.586688]             >>>>>>>  osync_group_env_new(8047d5c)
[1199894110.586723]             <<<<<<<  osync_group_env_new: 8068e00
[1199894110.586754]             >>>>>>>  osync_format_env_new(8047d5c)
[1199894110.586779]             <<<<<<<  osync_format_env_new: 8067fc0
[1199894110.586816]             >>>>>>>  osync_plugin_env_new(8047d5c)
[1199894110.586841]             <<<<<<<  osync_plugin_env_new: 8068780


Without those env variables, I can do "bb 1" but not "bb 2". Something
wrong with this syncml plugin I guess?





On Jan 9, 2008 12:58 AM, Daniel Gollub <dg...@su...> wrote:
> On Wednesday 09 January 2008 06:57:17 Anil wrote:
> > :)
> >
> > I cleaned up the build and recompiled. Still, msynctool core dumps
> > when I try to do a discover. Any ideas?
>
> Could you build OpenSync additionally with:
>
>  -DCMAKE_BUILD_TYPE=Debug
>
> or RelWithDebInfo if it isn't already...
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>

Re: [Opensync-users] msynctool discover cores

[Daniel G. <dg...@su...>]

On Wednesday 09 January 2008 06:57:17 Anil wrote:
> :)
>
> I cleaned up the build and recompiled. Still, msynctool core dumps
> when I try to do a discover. Any ideas?

Could you build OpenSync additionally with:

 -DCMAKE_BUILD_TYPE=Debug

or RelWithDebInfo if it isn't already...

Re: [Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

Sorry for the double post re the same problem. I am a little bit tired.
:)

I cleaned up the build and recompiled. Still, msynctool core dumps
when I try to do a discover. Any ideas?



On Jan 8, 2008 9:15 PM, jijun yu <Jij...@su...> wrote:
> Anil wrote:
> > I am just playing with this for the first time. Do you guys see
> > anything wrong with this configuration?
> >
> > Also, anyone have any problems building opensync on Solaris? For some
> > reason the "cmake -DCMAKE_INSTALL_PREFIX=/usr/local" commands did not
> > recognize the prefix and it wanted to install things in /lib, /share
> > etc. I had to go hack the cmake_install files.
> >
> It should be cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local
>
> >
> > vds5@vds5:~% msynctool --discover bb
> > Segmentation Fault (core dumped)
> >
> > vds5@vds5:~% pstack core
> > core 'core' of 20563:   msynctool --discover bb
> > -----------------  lwp# 1 / thread# 1  --------------------
> >  fed749ab __lwp_park (8068338, fef364bc, 8047b80) + b
> >  fed6f172 cond_wait_queue (8068338, fef364bc, 8047b80, 0) + 3b
> >  fed6f512 cond_wait_common (8068338, fef364bc, 8047b80) + 1df
> >  fed6f746 _cond_timedwait (8068338, fef364bc, 8047be4) + 51
> >  fed6f7b1 cond_timedwait (8068338, fef364bc, 8047be4) + 24
> >  fed6f7ed pthread_cond_timedwait (8068338, fef364bc, 8047be4) + 1e
> >  fee01217 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > -----------------  lwp# 4 / thread# 4  --------------------
> >  fed75387 __pollsys (8068798, 1, fe21bf20, 0) + 7
> >  fed1e94a poll     (8068798, 1, 1) + 52
> >  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > -----------------  lwp# 5 / thread# 5  --------------------
> >  fed75387 __pollsys (fe10fdf0, 1, fe10fdd0, 0) + 7
> >  fed1e94a poll     (fe10fdf0, 1, 64, fef363e8) + 52
> >  fef70284 osync_queue_poll (8070618, 0, fef363e8, fef70303, fef35748,
> > fe000000) + 3c
> >  fef703e7 _source_check (8071650, 80770d0, 0, 80770d0) + fb
> >  fef705f1 _source_dispatch (8071650, 0, 8070618) + 151
> >  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
> >  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
> >  53c300ff ???????? ()
> > -----------------  lwp# 6 / thread# 6  --------------------
> >  fed75387 __pollsys (80687d8, 1, fdffdf20, 0) + 7
> >  fed1e94a poll     (80687d8, 1, 1) + 52
> >  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > -----------------  lwp# 7 / thread# 7  --------------------
> >  feeee650 ???????? (0, fdefdbb4, fe5a648c, fdefdc6c, fed9e000, fe000800)
> >  feeefbd7 ???????? (fdefde48, 1, fe5a648c, fdefdc6c)
> >  fef50b4f osync_error_set (fdefde48, 1, fe5a648c, 0) + 23
> >  fe5a2d68 syncml_config_parse_database (fdefde48, fe5a634f, 807a2c8,
> > fee01472) + 194
> >  fe5a4c4b syncml_http_server_init (8079538, 807a1f8, fdefde48, 1) + 6e7
> >  fef7766b osync_plugin_initialize (8079538, 807a1f8, fdefde48,
> > 80710a0, 0, 0) + 23
> >  fef5530c _osync_client_handle_initialize (fdefde48, fef81098, c,
> > fef86bfb) + 204
> >  fef5620f _osync_client_message_handler (80770d0, 80710a0, fef7e6c0,
> > 8070618, 0, fef363e8) + 883
> >  fef6f1cd _incoming_dispatch (8073880, 0, 8070618) + 191
> >  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
> >  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
> >  53c300ff ???????? ()
> > -----------------  lwp# 8 / thread# 8  --------------------
> >  fed75387 __pollsys (fddfde80, 1, fddfde60, 0) + 7
> >  fed1e94a poll     (fddfde80, 1, 64, 806efe8) + 52
> >  fef70284 osync_queue_poll (8070f68, 0, feea1851, fef70303, 0, 0) + 3c
> >  fef703e7 _source_check (80751c0, 1, feec2881) + fb
> >  feec2a33 g_main_context_check (8458b1c, 8b34408b, e84c50, 5b000000,
> > 71d1c381, d2850002) + 1be
> >  ec835356 ???????? ()
> > -----------------  lwp# 9 / thread# 9  --------------------
> >  fed75387 __pollsys (8068808, 1, fdcfdf20, 0) + 7
> >  fed1e94a poll     (8068808, 1, 1) + 52
> >  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > vds5@vds5:~%
> >
> >
> >
> > vds5@vds5:~% msynctool --showgroup bb
> > Group: bb
> > Member 2: syncml-http-server
> >         Configuration : <?xml version="1.0"?>
> > <config>
> >   <!-- username to use. Leave empty to not require a username -->
> >   <username></username>
> >
> >   <!-- the password for the username -->
> >   <password></password>
> >
> >   <!-- The url that you want the server to listen on. This has to be
> > set on the mobile as well. example: "/" -->
> >   <url></url>
> >
> >   <!-- The port where to listen. This has to be set on the mobile as well. -->
> >   <port>8080</port>
> >
> >   <!-- If wbxml is enabled, defines wether the wbxml should use string
> > tables -->
> >   <usestringtable>0</usestringtable>
> >
> >   <!-- Never send ADD command, but send REPLACE (not needed normally) -->
> >   <onlyreplace>0</onlyreplace>
> >
> >   <!-- Workaround around for mobile phones which only use local
> > timestamps and _no_ UTC timestamps! -->
> >   <onlyLocaltime>0</onlyLocaltime>
> >
> >   <!-- Sets the maximum allowed size in bytes of incoming messages
> > (some device need this option set). Example: 10000 -->
> >   <recvLimit>0</recvLimit>
> >
> >   <maxObjSize>0</maxObjSize>
> >
> >   <!-- Contact database -->
> >   <database>
> >      <name>Contacts</name>
> >      <objtype>contact</objtype>
> >   </database>
> >
> >   <!-- Calendar database -->
> >   <database>
> >      <name>Calendar</name>
> >      <objtype>event</objtype>
> >   </database>
> >
> >
> >   <!-- Note database -->
> >   <!--
> >   <database>
> >      <name>Notes</name>
> >      <objtype>note</objtype>
> >   </database>
> >   -->
> >
> > </config>
> >
> > Member 1: file-sync
> >         Configuration : <?xml version="1.0"?>
> > <config>
> >   <directory>
> >     <path>/home/vds5/sync1</path>
> >     <objtype>data</objtype>
> >   </directory>
> >
> >   <!--
> >
> >    Field objformat set the object format which should be used to store.
> >    objformat is optional - by default objformat is "file".
> >
> >   -->
> >
> >   <directory>
> >     <path>/home/vds5/sync1</path>
> >     <objtype>contact</objtype>
> >     <objformat>vcard30</objformat>
> >   </directory>
> >
> >   <directory>
> >     <path>/home/vds5/sync1</path>
> >     <objtype>event</objtype>
> >     <objformat>vevent20</objformat>
> >   </directory>
> >
> > </config>
> >
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
> >
>
>

Re: [Opensync-users] cmake doesn't use prefix

[jijun yu <Jij...@Su...>]

You can try to remove the files created at build time  and then use "

/opt/csw/bin/cmake
-DCMAKE_INSTALL_PREFIX:PATH=/usr/local ../ (Here a *PATH* was added)

. It should work.

- Jerry

Anil wrote:
> vds5@vds5:~/msynctool-0.35/build% /opt/csw/bin/cmake
> -DCMAKE_INSTALL_PREFIX=/usr/local ../
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /home/vds5/msynctool-0.35/build
>
> Notice how its installing to /bin/msynctool instead of /usr/local/bin/msynctool:
>
> vds5@vds5:~/msynctool-0.35/build% make install
> Linking C executable msynctool
> [100%] Built target msynctool
> Linking C executable CMakeFiles/CMakeRelink.dir/msynctool
> Install the project...
> -- Install configuration: "RelWithDebInfo"
> -- Installing /bin/msynctool
> CMake Error: Error in cmake code at
> /home/vds5/msynctool-0.35/build/tools/cmake_install.cmake:30:
> FILE INSTALL cannot copy file
> "/home/vds5/msynctool-0.35/build/tools/CMakeFiles/CMakeRelink.dir/msynctool"
> to "/bin/msynctool".
> Current CMake stack:
> [2]     /home/vds5/msynctool-0.35/build/tools/cmake_install.cmake
> [1]     /home/vds5/msynctool-0.35/build/cmake_install.cmake
> *** Error code 255
> The following command caused the error:
> /opt/csw/bin/cmake -P cmake_install.cmake
> make: Fatal error: Command failed for target `install'
> vds5@vds5:~/msynctool-0.35/build%
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>   

Re: [Opensync-users] msynctool discover cores

[jijun yu <Jij...@Su...>]

Anil wrote:
> I am just playing with this for the first time. Do you guys see
> anything wrong with this configuration?
>
> Also, anyone have any problems building opensync on Solaris? For some
> reason the "cmake -DCMAKE_INSTALL_PREFIX=/usr/local" commands did not
> recognize the prefix and it wanted to install things in /lib, /share
> etc. I had to go hack the cmake_install files.
>   
It should be cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local
>
> vds5@vds5:~% msynctool --discover bb
> Segmentation Fault (core dumped)
>
> vds5@vds5:~% pstack core
> core 'core' of 20563:   msynctool --discover bb
> -----------------  lwp# 1 / thread# 1  --------------------
>  fed749ab __lwp_park (8068338, fef364bc, 8047b80) + b
>  fed6f172 cond_wait_queue (8068338, fef364bc, 8047b80, 0) + 3b
>  fed6f512 cond_wait_common (8068338, fef364bc, 8047b80) + 1df
>  fed6f746 _cond_timedwait (8068338, fef364bc, 8047be4) + 51
>  fed6f7b1 cond_timedwait (8068338, fef364bc, 8047be4) + 24
>  fed6f7ed pthread_cond_timedwait (8068338, fef364bc, 8047be4) + 1e
>  fee01217 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> -----------------  lwp# 4 / thread# 4  --------------------
>  fed75387 __pollsys (8068798, 1, fe21bf20, 0) + 7
>  fed1e94a poll     (8068798, 1, 1) + 52
>  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> -----------------  lwp# 5 / thread# 5  --------------------
>  fed75387 __pollsys (fe10fdf0, 1, fe10fdd0, 0) + 7
>  fed1e94a poll     (fe10fdf0, 1, 64, fef363e8) + 52
>  fef70284 osync_queue_poll (8070618, 0, fef363e8, fef70303, fef35748,
> fe000000) + 3c
>  fef703e7 _source_check (8071650, 80770d0, 0, 80770d0) + fb
>  fef705f1 _source_dispatch (8071650, 0, 8070618) + 151
>  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
>  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
>  53c300ff ???????? ()
> -----------------  lwp# 6 / thread# 6  --------------------
>  fed75387 __pollsys (80687d8, 1, fdffdf20, 0) + 7
>  fed1e94a poll     (80687d8, 1, 1) + 52
>  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> -----------------  lwp# 7 / thread# 7  --------------------
>  feeee650 ???????? (0, fdefdbb4, fe5a648c, fdefdc6c, fed9e000, fe000800)
>  feeefbd7 ???????? (fdefde48, 1, fe5a648c, fdefdc6c)
>  fef50b4f osync_error_set (fdefde48, 1, fe5a648c, 0) + 23
>  fe5a2d68 syncml_config_parse_database (fdefde48, fe5a634f, 807a2c8,
> fee01472) + 194
>  fe5a4c4b syncml_http_server_init (8079538, 807a1f8, fdefde48, 1) + 6e7
>  fef7766b osync_plugin_initialize (8079538, 807a1f8, fdefde48,
> 80710a0, 0, 0) + 23
>  fef5530c _osync_client_handle_initialize (fdefde48, fef81098, c,
> fef86bfb) + 204
>  fef5620f _osync_client_message_handler (80770d0, 80710a0, fef7e6c0,
> 8070618, 0, fef363e8) + 883
>  fef6f1cd _incoming_dispatch (8073880, 0, 8070618) + 191
>  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
>  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
>  53c300ff ???????? ()
> -----------------  lwp# 8 / thread# 8  --------------------
>  fed75387 __pollsys (fddfde80, 1, fddfde60, 0) + 7
>  fed1e94a poll     (fddfde80, 1, 64, 806efe8) + 52
>  fef70284 osync_queue_poll (8070f68, 0, feea1851, fef70303, 0, 0) + 3c
>  fef703e7 _source_check (80751c0, 1, feec2881) + fb
>  feec2a33 g_main_context_check (8458b1c, 8b34408b, e84c50, 5b000000,
> 71d1c381, d2850002) + 1be
>  ec835356 ???????? ()
> -----------------  lwp# 9 / thread# 9  --------------------
>  fed75387 __pollsys (8068808, 1, fdcfdf20, 0) + 7
>  fed1e94a poll     (8068808, 1, 1) + 52
>  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> vds5@vds5:~%
>
>
>
> vds5@vds5:~% msynctool --showgroup bb
> Group: bb
> Member 2: syncml-http-server
>         Configuration : <?xml version="1.0"?>
> <config>
>   <!-- username to use. Leave empty to not require a username -->
>   <username></username>
>
>   <!-- the password for the username -->
>   <password></password>
>
>   <!-- The url that you want the server to listen on. This has to be
> set on the mobile as well. example: "/" -->
>   <url></url>
>
>   <!-- The port where to listen. This has to be set on the mobile as well. -->
>   <port>8080</port>
>
>   <!-- If wbxml is enabled, defines wether the wbxml should use string
> tables -->
>   <usestringtable>0</usestringtable>
>
>   <!-- Never send ADD command, but send REPLACE (not needed normally) -->
>   <onlyreplace>0</onlyreplace>
>
>   <!-- Workaround around for mobile phones which only use local
> timestamps and _no_ UTC timestamps! -->
>   <onlyLocaltime>0</onlyLocaltime>
>
>   <!-- Sets the maximum allowed size in bytes of incoming messages
> (some device need this option set). Example: 10000 -->
>   <recvLimit>0</recvLimit>
>
>   <maxObjSize>0</maxObjSize>
>
>   <!-- Contact database -->
>   <database>
>      <name>Contacts</name>
>      <objtype>contact</objtype>
>   </database>
>
>   <!-- Calendar database -->
>   <database>
>      <name>Calendar</name>
>      <objtype>event</objtype>
>   </database>
>
>
>   <!-- Note database -->
>   <!--
>   <database>
>      <name>Notes</name>
>      <objtype>note</objtype>
>   </database>
>   -->
>
> </config>
>
> Member 1: file-sync
>         Configuration : <?xml version="1.0"?>
> <config>
>   <directory>
>     <path>/home/vds5/sync1</path>
>     <objtype>data</objtype>
>   </directory>
>
>   <!--
>
>    Field objformat set the object format which should be used to store.
>    objformat is optional - by default objformat is "file".
>
>   -->
>
>   <directory>
>     <path>/home/vds5/sync1</path>
>     <objtype>contact</objtype>
>     <objformat>vcard30</objformat>
>   </directory>
>
>   <directory>
>     <path>/home/vds5/sync1</path>
>     <objtype>event</objtype>
>     <objformat>vevent20</objformat>
>   </directory>
>
> </config>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>   

[Opensync-users] cmake doesn't use prefix

[Anil <rep...@gm...>]

vds5@vds5:~/msynctool-0.35/build% /opt/csw/bin/cmake
-DCMAKE_INSTALL_PREFIX=/usr/local ../
-- Configuring done
-- Generating done
-- Build files have been written to: /home/vds5/msynctool-0.35/build

Notice how its installing to /bin/msynctool instead of /usr/local/bin/msynctool:

vds5@vds5:~/msynctool-0.35/build% make install
Linking C executable msynctool
[100%] Built target msynctool
Linking C executable CMakeFiles/CMakeRelink.dir/msynctool
Install the project...
-- Install configuration: "RelWithDebInfo"
-- Installing /bin/msynctool
CMake Error: Error in cmake code at
/home/vds5/msynctool-0.35/build/tools/cmake_install.cmake:30:
FILE INSTALL cannot copy file
"/home/vds5/msynctool-0.35/build/tools/CMakeFiles/CMakeRelink.dir/msynctool"
to "/bin/msynctool".
Current CMake stack:
[2]     /home/vds5/msynctool-0.35/build/tools/cmake_install.cmake
[1]     /home/vds5/msynctool-0.35/build/cmake_install.cmake
*** Error code 255
The following command caused the error:
/opt/csw/bin/cmake -P cmake_install.cmake
make: Fatal error: Command failed for target `install'
vds5@vds5:~/msynctool-0.35/build%

[Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

I am just playing with this for the first time. Do you guys see
anything wrong with this configuration?

Also, anyone have any problems building opensync on Solaris? For some
reason the "cmake -DCMAKE_INSTALL_PREFIX=/usr/local" commands did not
recognize the prefix and it wanted to install things in /lib, /share
etc. I had to go hack the cmake_install files.


vds5@vds5:~% msynctool --discover bb
Segmentation Fault (core dumped)

vds5@vds5:~% pstack core
core 'core' of 20563:   msynctool --discover bb
-----------------  lwp# 1 / thread# 1  --------------------
 fed749ab __lwp_park (8068338, fef364bc, 8047b80) + b
 fed6f172 cond_wait_queue (8068338, fef364bc, 8047b80, 0) + 3b
 fed6f512 cond_wait_common (8068338, fef364bc, 8047b80) + 1df
 fed6f746 _cond_timedwait (8068338, fef364bc, 8047be4) + 51
 fed6f7b1 cond_timedwait (8068338, fef364bc, 8047be4) + 24
 fed6f7ed pthread_cond_timedwait (8068338, fef364bc, 8047be4) + 1e
 fee01217 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
-----------------  lwp# 4 / thread# 4  --------------------
 fed75387 __pollsys (8068798, 1, fe21bf20, 0) + 7
 fed1e94a poll     (8068798, 1, 1) + 52
 feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
-----------------  lwp# 5 / thread# 5  --------------------
 fed75387 __pollsys (fe10fdf0, 1, fe10fdd0, 0) + 7
 fed1e94a poll     (fe10fdf0, 1, 64, fef363e8) + 52
 fef70284 osync_queue_poll (8070618, 0, fef363e8, fef70303, fef35748,
fe000000) + 3c
 fef703e7 _source_check (8071650, 80770d0, 0, 80770d0) + fb
 fef705f1 _source_dispatch (8071650, 0, 8070618) + 151
 feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
 feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
 53c300ff ???????? ()
-----------------  lwp# 6 / thread# 6  --------------------
 fed75387 __pollsys (80687d8, 1, fdffdf20, 0) + 7
 fed1e94a poll     (80687d8, 1, 1) + 52
 feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
-----------------  lwp# 7 / thread# 7  --------------------
 feeee650 ???????? (0, fdefdbb4, fe5a648c, fdefdc6c, fed9e000, fe000800)
 feeefbd7 ???????? (fdefde48, 1, fe5a648c, fdefdc6c)
 fef50b4f osync_error_set (fdefde48, 1, fe5a648c, 0) + 23
 fe5a2d68 syncml_config_parse_database (fdefde48, fe5a634f, 807a2c8,
fee01472) + 194
 fe5a4c4b syncml_http_server_init (8079538, 807a1f8, fdefde48, 1) + 6e7
 fef7766b osync_plugin_initialize (8079538, 807a1f8, fdefde48,
80710a0, 0, 0) + 23
 fef5530c _osync_client_handle_initialize (fdefde48, fef81098, c,
fef86bfb) + 204
 fef5620f _osync_client_message_handler (80770d0, 80710a0, fef7e6c0,
8070618, 0, fef363e8) + 883
 fef6f1cd _incoming_dispatch (8073880, 0, 8070618) + 191
 feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
 feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
 53c300ff ???????? ()
-----------------  lwp# 8 / thread# 8  --------------------
 fed75387 __pollsys (fddfde80, 1, fddfde60, 0) + 7
 fed1e94a poll     (fddfde80, 1, 64, 806efe8) + 52
 fef70284 osync_queue_poll (8070f68, 0, feea1851, fef70303, 0, 0) + 3c
 fef703e7 _source_check (80751c0, 1, feec2881) + fb
 feec2a33 g_main_context_check (8458b1c, 8b34408b, e84c50, 5b000000,
71d1c381, d2850002) + 1be
 ec835356 ???????? ()
-----------------  lwp# 9 / thread# 9  --------------------
 fed75387 __pollsys (8068808, 1, fdcfdf20, 0) + 7
 fed1e94a poll     (8068808, 1, 1) + 52
 feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
vds5@vds5:~%



vds5@vds5:~% msynctool --showgroup bb
Group: bb
Member 2: syncml-http-server
        Configuration : <?xml version="1.0"?>
<config>
  <!-- username to use. Leave empty to not require a username -->
  <username></username>

  <!-- the password for the username -->
  <password></password>

  <!-- The url that you want the server to listen on. This has to be
set on the mobile as well. example: "/" -->
  <url></url>

  <!-- The port where to listen. This has to be set on the mobile as well. -->
  <port>8080</port>

  <!-- If wbxml is enabled, defines wether the wbxml should use string
tables -->
  <usestringtable>0</usestringtable>

  <!-- Never send ADD command, but send REPLACE (not needed normally) -->
  <onlyreplace>0</onlyreplace>

  <!-- Workaround around for mobile phones which only use local
timestamps and _no_ UTC timestamps! -->
  <onlyLocaltime>0</onlyLocaltime>

  <!-- Sets the maximum allowed size in bytes of incoming messages
(some device need this option set). Example: 10000 -->
  <recvLimit>0</recvLimit>

  <maxObjSize>0</maxObjSize>

  <!-- Contact database -->
  <database>
     <name>Contacts</name>
     <objtype>contact</objtype>
  </database>

  <!-- Calendar database -->
  <database>
     <name>Calendar</name>
     <objtype>event</objtype>
  </database>


  <!-- Note database -->
  <!--
  <database>
     <name>Notes</name>
     <objtype>note</objtype>
  </database>
  -->

</config>

Member 1: file-sync
        Configuration : <?xml version="1.0"?>
<config>
  <directory>
    <path>/home/vds5/sync1</path>
    <objtype>data</objtype>
  </directory>

  <!--

   Field objformat set the object format which should be used to store.
   objformat is optional - by default objformat is "file".

  -->

  <directory>
    <path>/home/vds5/sync1</path>
    <objtype>contact</objtype>
    <objformat>vcard30</objformat>
  </directory>

  <directory>
    <path>/home/vds5/sync1</path>
    <objtype>event</objtype>
    <objformat>vevent20</objformat>
  </directory>

</config>

Re: [Opensync-users] Problems with libsyncml

[Michael B. <mic...@cm...>]

Daniel Gollub schrieb:

> I just had a quick look on the syncml log dumps. I guess following SyncML 
> message generated by libsyncml is wrong (sent-1.xml):
> 
> <SyncBody>
>     <Status>
>         ...
>         <SourceRef>Sony Ericss</SourceRef>
>         <TargetRef>IMEI:xxxxxxxxxxxxxx</TargetRef>
>        ....
>     </Status>
>     ....
> </SyncBody>
>
> Actually your identifier string should be in that context the <TargetRef/>, 
> and the IMEI string in <SourceRef/>. Since the Status refers from a SyncML 
> command which got emitted by the mobile. And for the mobile the Target is 
> libsyncml ...

This is correct. The bug is in sml_auth.c where it creates a new status. 
The used session is used with the wrong viewpoint (local site instead of 
the remote peer).

> I'll review the commits to see when this bug got introduced... not quite sure 
> if r263 is affected or not.

I fixed it in r320. This is a single commit of one file - so it is human 
readable :)

Best regards

Michael
-- 
_______________________________________________________________

Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704       Unter den Linden 6
mic...@cm...   D-10099 Berlin
_______________________________________________________________

X.509 CA Certificates / Wurzelzertifikate

http://ra.pki.hu-berlin.de

Re: [Opensync-users] Backing up N73 messages (SMS, MMS)

[Daniel G. <dg...@su...>]

On Dienstag 08 Januar 2008, Michael Bell wrote:
> > Arg, yes - that could be as well.. since the latest syncml-obex-client
> > might already send it's own capailities in advance. SyncML Spec says that
> > the device then only should reply supported capabilities by the device...
>
> Why should this happen?
AFAIK, syncml-obex-client has hardcoded datasore support for text/x-vcard, 
text/x-vcalendar and text/plain. If those got set with --slow-sync or --sync 
say got set as preferred type.

Shouldn't be that enough that libsyncml would send the capabilities in 
advnance.. not quite sure about the latest changes in libsyncml. I have to 
take a look on that...

>
> > Not quite sure if syncml-obex-client is already sending the (own) entire
> > capabilities in advance or not.. it's up to your version of libsyncml.
> > Michael Bell that recently lots of development in this area ... we need
> > have to introduce finally same proper discovery function for
> > syncml-obex-client tool (and OpenSync plugin). Not quite sure how hard
> > this is to implement.
>
> The syncml-obex-client is in fact a SyncML server according to the
> protocol. The name is a little bit misleading. I can only test the http
> stuff and here always the SyncML client sends the first DevInf.

Yeah the naming is indeed confusing, it's more related to the transport role. 
The actually correct name would be:

syncml-server-obex-client

Maybe we should rename the process and the plugin. Same for the http transport 
plugins... to sum it up it would be possible to have:

syncml-client-obex-client
syncml-server-obex-client  (aka. syncml-obex-client)

syncml-client-http-client (aka. syncml-http-client)
syncml-server-http-server (aka. syncml-http-server)

Correct?

best regards,
Daniel

Re: [Opensync-users] Backing up N73 messages (SMS, MMS)

[Michael B. <mic...@cm...>]

Daniel Gollub schrieb:

> Arg, yes - that could be as well.. since the latest syncml-obex-client might 
> already send it's own capailities in advance. SyncML Spec says that the 
> device then only should reply supported capabilities by the device...

Why should this happen?

> Not quite sure if syncml-obex-client is already sending the (own) entire 
> capabilities in advance or not.. it's up to your version of libsyncml. 
> Michael Bell that recently lots of development in this area ... we need have 
> to introduce finally same proper discovery function for syncml-obex-client 
> tool (and OpenSync plugin). Not quite sure how hard this is to implement.

The syncml-obex-client is in fact a SyncML server according to the 
protocol. The name is a little bit misleading. I can only test the http 
stuff and here always the SyncML client sends the first DevInf.

I use SyncML over http over bluetooth and sniff it with wireshark. If 
you do this with OBEX instead of http then you should see which sends 
the first devinf.

Best regards

Michael
-- 
_______________________________________________________________

Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704       Unter den Linden 6
mic...@cm...   D-10099 Berlin
_______________________________________________________________

X.509 CA Certificates / Wurzelzertifikate

http://ra.pki.hu-berlin.de

Re: [Opensync-users] Backing up N73 messages (SMS, MMS)

[Daniel G. <dg...@su...>]

On Dienstag 08 Januar 2008, Nicholas Piper wrote:
> It looks like CTCap for me only shows the mimetypes of the databases
> I've selected already, so I can't discover new ones this way.
>
> What I did learn today, is that the S60 --identifier is not matching
> the phone synchronisation profile name, but actually the "Host
> address"!

Arg, yes - that could be as well.. since the latest syncml-obex-client might 
already send it's own capailities in advance. SyncML Spec says that the 
device then only should reply supported capabilities by the device...

Not quite sure if syncml-obex-client is already sending the (own) entire 
capabilities in advance or not.. it's up to your version of libsyncml. 
Michael Bell that recently lots of development in this area ... we need have 
to introduce finally same proper discovery function for syncml-obex-client 
tool (and OpenSync plugin). Not quite sure how hard this is to implement.

>
> > text/x-vMessage
> >
> > If you find text/x-vMessage or somehihng simliar just try:
> >
> > syncml-obex-client --slow-sync text/x-vMessages RandomLocalDatabaseName
> > ....
>
> I think "syncml-obex-client --identifier 'my sync' -b
> 00:19:79:CE:B8:FD 10 --wbxml --sync text/x-vMessages sms" may work,
> however the phone just shows "Connecting" for ages. I think maybe I
> have too many entries on the phone? I cleared the INBOX into folders,
> but maybe it still uses those (I hope so, actually.)
>
> Eventually the sync with text/x-vMessages shows "Operation time-out"
> on the handset. The received-0.xml log is at
> http://pastebin.com/m200e5897 (ignore the − parts, sorry.)

Looks interesting... could you check SYNCML_TRACE as well.. might me that the 
xml parser or assembler fails and libsyncml fails to recover from the 
parser/assmebler error...

>
> I can't delete all the messages to try with a cleaner handset, because
> I can't back them up...

Does libsyncml send at least another package back to the device? Is there an 
sent-N+1.xml?

>
> However, for syncing more types of my content, "Lifeblog" seems to be
> a database on the phone with MMS, photos, SMS, etc. etc. I just don't
> know what mimetype to use in the obex-client?
>
> I tried "application/atom+xml" and "application/x.atom+xml", as well
> as text/xml, application/xml, etc.
>
> Maybe I need to set up Lifeblog on a Windows PC and sniff a sync with
> that.
This would help for sure...

best regards,
Daniel

Re: [Opensync-users] Syncing notes (on Nokia 6300)

[Daniel G. <dg...@su...>]

On Dienstag 08 Januar 2008, Jason Grant wrote:
> =A0 <database>
> =A0 =A0 =A0<name>Notes</name>
> =A0 =A0 =A0<objtype>note</objtype>
> =A0 =A0 =A0<objformat>vjournal</objformat>
> =A0 </database>

Try <objformat>memo</objformat> instead ..

Memo has the same function like the "plain" object format, but is mapped to=
=20
the object type "note" instead of "data". objformat "vjournal" is the used=
=20
objformat by evolution for notes, vjournal is based on rfc2445, thats why y=
ou=20
see BEGIN:VCALENDAR ...

With memo the conversion path during sync should look like this:

vjournal <-> xmlformat-note <-> memo


>
> Is this the correct format to be using?
>
> To try and troubleshoot this, I downloaded devinfo.txt from the handset
> as shown below. =A0I'm now wondering whether the fact that the NOTE
> records are labelled as NONE means that the handset cannot cope with
> vcalendar formatting, and that only the raw note data should be resident
> on the phone?
>
> Thanks for any tips/guidance.
>
> Jason.
>
>
> ----------- devinfo.txt ----------------
> MANU:Nokia
> MOD:RM-217
> HW-VERSION:1007
> SW-VERSION:V 05.50
> SW-DATE:20070814T120000
> SN:359835011196264
> IRMC-VERSION:1.1
> PB-TYPE-TX:VCARD2.1
> PB-TYPE-RX:VCARD2.1;VCARD3.0
> CAL-TYPE-TX:VCALENDAR1.0
> CAL-TYPE-RX:VCALENDAR1.0;ICALENDAR2.0
> INBOX:SINGLE
> MSG-TYPE-TX:NONE
> MSG-TYPE-RX:NONE
> MSG-SENT-BOX:NO
> NOTE-TYPE-TX:NONE
> NOTE-TYPE-RX:NONE
> BKM-TYPE-TX:NONE
> BKM-TYPE-RX:NONE
> X-TEXT:NOKIA1.0
> X-POC:NOKIA1.0
> IAS-PARAMETERS:0x00,0x01,0x02,0x01,0x01,0x00,0x02,0x02,0x01,0x01,0x10,
> =A00x01,0x08,0x11,0x02,0x01,0x01,0x12,0x01,0x00

Where did you got this? Looks like IrMC's devinfo.txt ... the capabilities =
for=20
IrMC might differ from the SyncML ...

best regards,
Daniel