Hi Schooner:
    Thanks for your quick reply. I think I known where was going wrong! I 
checked the machinekit.ini file as you told me. this file was empty. That's 
why rtapi needs UUID. I guess there was some thing wrong when I was 
compiling machinekit source code. So I recompiled it. And this time I got 
machineit.ini file.  Now every thing works fine! 
    Thank you for your detailed guide!
    Letian   

在 2018年1月17日星期三 UTC+8下午9:43:31,Schooner写道:
>
> Regards the error
>
> If you have built from sources, machinekit.ini and rtapi.ini are in 
> machinekit/etc/
>
> Most common error is not the set the environment in *the terminal* which 
> you try to open machinekit in.
> ie.
> Having built machinekit and setuid 
> cd ../
> . ./scripts/rip-environment
> machinekit
>
> all in the *same* terminal session.
>
> Also if you setuid after compiling machinekit for the first time on that 
> computer, it will not have worked
> and you need to create /var/log/linuxcnc.log and restart rsyslogd etc. etc.
>
> The script that checks is here
>
> https://github.com/machinekit/machinekit/blob/master/scripts/check-system-configuration.sh#L23
> and if any element is missing setuid is aborted
>
> There is a print of errors when you run setuid and you can cut and paste 
> the commands from them.
> Then run sudo setuid again, because it did not work the first time if you 
> got those errors.
>
> This is not the error you posted, setuid and UUID are 2 different things, 
> but just checking the build did in fact get finished properly
> before moving to any new errors and seeing what config you are trying to 
> run.
>
>
> On 17/01/18 10:12, [email protected] <javascript:> wrote:
>
> The error comes from here 
> https://github.com/machinekit/machinekit/blob/master/src/rtapi/rtapi_app.cc#L1717
> (note it tries to parse the ini file, what is in yours?)
>
> Without the full errors and view of what you are trying to run can't help 
> further.
>
>
> On 17/01/18 09:59, Letian Fang wrote:
>
>     Hi guys: 
>     I have installed my new debian stretch on my laptop pc. I have 
> compiled machinekit using posix flavor as followed the instruction by 
> www.machinekit.io/docs/:
>     debian/configure -p  // just want use posix thread to run a simulation
>     sudo mk-build-deps -ir
>     cd src
>     ./autogen.sh
>     ./configure --with-posix
>     ... ...
>     after everything is done. I launched machinekit using shell 
> command:machinekit
>     And it turn's out :
>     Starting Machinekit:
>     rtapi: no service UUID ....
>     rtapi_app startup failed ....
>     halcmd: no service UUID ...
>     I've used sudo make setuid, and still It does not work!
>
>     So please, May I ask why? And How to solve this problem?
>    
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to