View Single Post
Posts: 107 | Thanked: 173 times | Joined on Feb 2011
#144
Originally Posted by qwazix View Post
I'm debugging this right now and I think the problem is that timenow starts before proximityd. So I modified the upstart job to look like this.

The fact that it happens to some people and not other is probably due to the different startup services of each setup.
If this can help anyone, I can start timenow before proximityd and everything is fine.
On the other hand, proximityd was not started on boot despite the /etc/event.d/proximityd file. After some tests, I discovered that the proximityd start script did not grab the right dbus-daemon pid in order to launch proximityd correctly. I added the following line after the "respawn" line and proximityd is now started correctly on boot:
Code:
respawn limit 15 3
 

The Following 3 Users Say Thank You to pierrem For This Useful Post: