|
2014-01-20
, 15:29
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#232
|
The Following User Says Thank You to qwazix For This Useful Post: | ||
|
2014-01-20
, 18:11
|
Posts: 159 |
Thanked: 217 times |
Joined on Oct 2011
|
#233
|
|
2014-01-22
, 07:25
|
Posts: 159 |
Thanked: 217 times |
Joined on Oct 2011
|
#234
|
|
2014-01-24
, 22:43
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#235
|
ps aux | grep proximity
|
2014-01-25
, 11:09
|
Posts: 159 |
Thanked: 217 times |
Joined on Oct 2011
|
#236
|
|
2014-02-16
, 10:01
|
|
Posts: 83 |
Thanked: 115 times |
Joined on Nov 2012
@ Sweden
|
#237
|
|
2014-02-16
, 18:48
|
Posts: 159 |
Thanked: 217 times |
Joined on Oct 2011
|
#238
|
The Following User Says Thank You to Kossuth For This Useful Post: | ||
|
2014-03-15
, 11:59
|
|
Posts: 83 |
Thanked: 115 times |
Joined on Nov 2012
@ Sweden
|
#239
|
|
2014-03-15
, 17:14
|
|
Posts: 83 |
Thanked: 115 times |
Joined on Nov 2012
@ Sweden
|
#240
|
I havent got the time to properly troubleshoot the situation, but it seems that restarting the timenow.conf does not solve it, only restarting the proximityd does it. It also seems that the proximityd is alive when I restart it to get it workin, because I can also stop it without errors when timenow stops responding.
Is proximityd part of timenow or is it standalone part by someone else? Is there use to try to check any logs or that kind of stuff about the communication between timenow and proximityd?