View Single Post
Posts: 1,100 | Thanked: 2,797 times | Joined on Apr 2011 @ Netherlands
#897
Originally Posted by yablacky View Post
You say that - in contrast to the error message - the daemon is running. I guess you used the ps command to check that out. Could you please repeat the situation on your device and post the outcome of the ps command here?

Code:
$ # if you like to post the full list:
$ ps > file_to_post


$ # if you like to post only what is of interest for me:
$ ps | grep smscon > file_to_post
Thank you.
Well, a daemon gets started, but in combination with the error message. Another attempt to start spawns a new daemon.

After the first attempt to start smscon using smscon-editor:
Code:
user     21565  1436  7 12:55 ?        00:00:04 python /opt/smscon-editor/smscon-editor
root     21602     1  3 12:56 ?        00:00:00 python /opt/smscon/smscon_daemon
When I get the error, I go for a second attempt to start the deamon. Again the error, with a new process:
Code:
user     21565  1436  5 12:55 ?        00:00:04 python /opt/smscon-editor/smscon-editor
root     21602     1  1 12:56 ?        00:00:00 python /opt/smscon/smscon_daemon
root     21670     1 10 12:57 ?        00:00:00 python /opt/smscon/smscon_daemon
 

The Following 2 Users Say Thank You to ade For This Useful Post: