If you kill an application it does not shutdown cleanly. Machinekit does not like to be killed so there might be some memlocks still allocated. realtime stop usually helps in such situations
Devin Hughes writes: > Hello, > > I've been writing a port to interact with machinetalk and I hit some > behavior I don't understand with mklauncher. I can successfully enumerate > launchers, start launchers, terminate launchers, etc., but when I send a > kill command I get strange results. The running machinekit instance is > stopped, but when I try to start a new one I get the error > > msgd:0: mlock(global) failed: 12 'Cannot allocate memory' > > This does not happen when I call the terminate rpc - I can freely start and > stop as many times as I'd like. Is this expected behavior? Are there side > effects of calling kill that changes the link to /etc/security/.. memory > config for machinekit? > > Thanks for any guidance. > > Devin -- 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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
