maemo.org - Talk - View Single Post - [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

MasterZap	2011-05-24 , 11:27
Posts: 214 \| Thanked: 140 times \| Joined on Aug 2010	#136

Originally Posted by Gusse

Yes I have. Is this a problem? Should I revert back?

Other people have had the same issue w. new busybox, but it was due to a wrong "ps -e | grep" line I used (-e not a proper option in new busybox, and it was wrong anyway, was supposed to be -a)

However, that should have been fixed in 39... :/ Strange.

Originally Posted by Gusse

Using 0.9.4-39.
If background service is OFF, then it shutdown OK (no ghost program running in backgroung)
If background service is ON, then
Code:
~ $ ps -w|grep "zaploc-daemon"
3815 user 50968 S /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
3951 user 50820 S /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
4066 user 50824 S /usr/bin/python /opt/zaploc/zaploc-daemon.py -d
4130 user 2832 S grep zaploc-daemon
Above is after 3rd time closing ZapLoc. Each time a new daemon is added.

What's "-w", I wonder? "-a" (all users) is what I would have expected to use....?

If you start ZapLoc from xterm and see what it prints ("Starting Daemon", "Stopping Daemon" etc. like that) would be helpful. Ideally run as "user", not "root".

Actually the exact output of this would be very helpful:

Code:

ps -a | grep "python.*zaploc-daemon.py" | grep -v grep | awk '{print $1}'

Last edited by MasterZap; 2011-05-24 at 11:37.

Quote & Reply |

The Following User Says Thank You to MasterZap For This Useful Post:
Gusse