12:32 p.m.
Hi all,
I have SyncEvolution and my DroidX happily chatting with each other but
now I have another question. How to start the server automatically at
boot time.
I made an /etc/rc.d script that started the server just fine but it
starts the server in the root context. I found that out by watching
SyncML on my Droid delete everything because, of course, there are no
Evolution databases for root.
I tried starting it using Gnome's start-up tasks options. That also
started the server but it could not access access tasks nor notes
(access denied).
So now I start it manually after reboot with
nohup sudo syncevo-http-server -d http://localhost:9000/syncevolution &
Which works perfectly but requires me to remember to do it each time I boot.
Any suggestions on how to automate this?
Thanks,
John
--
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com <-- THE source for induction heaters
http://www.neon-john.com <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77
2:08 p.m.
On Tue, 2014-07-29 at 08:32 -0400, NeonJohn wrote:
Hi all,
I have SyncEvolution and my DroidX happily chatting with each other but
now I have another question. How to start the server automatically at
boot time.
I made an /etc/rc.d script that started the server just fine but it
starts the server in the root context. I found that out by watching
SyncML on my Droid delete everything because, of course, there are no
Evolution databases for root.
I tried starting it using Gnome's start-up tasks options. That also
started the server but it could not access access tasks nor notes
(access denied).
It should work, so it would be worth investigating where the "access
denied" error comes from.
If you start this way, which processes are running? Check with "ps -ef |
grep -e evolution -e syncevo".
Does "syncevolution --print-databases" work?
What does the latest syncevolution-log.html under ~/.cache/syncevolution
say about the sync?
So now I start it manually after reboot with
nohup sudo syncevo-http-server -d http://localhost:9000/syncevolution &
"sudo" should not be necessary. I suspect it happens to work because it
runs syncevo-http-server as root with access to your normal user's D-Bus
session, and the rest of the system (EDS, syncevo-dbus-server) actually
run as normal user. Please verify with the same ps command as above.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
2715
days inactive
2735
days old
syncevolution@synevolution.org
1 comments
2 participants
participants (2)
-
NeonJohn -
Patrick Ohly