Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

With Resin 2.1 used to run make; make install and then use the binary bin/resin to start Resin, but in Resin 3.0 I can find the binary. What happened to it?

April 26, 2017Bin binary install resin run Used

0

Posted

With Resin 2.1 used to run make; make install and then use the binary bin/resin to start Resin, but in Resin 3.0 I can find the binary. What happened to it?

1 Answer

0

Posted

Resin 2.1 used the bin/resin binary to enable two features: JNI usage (including OpenSSL) and to support and for switching the effective user id of the process after attaching to ports under 1024. Resin now uses the JNI library from within Java. You don’t need a compiled binary to get at the JNI code (that was bin/resin in 2.1.x). So, the java process starts up and then hooks into the JNI libraries. Resin uses JNI for: • OpenSSL • low level system calls, for things like socket connections etc. (for performance reasons). So Resin can run without the JNI libraries, it just won’t be as Resin as Resin. user-name and group-name support no longer need the resin binary either. The only place it won’t work is on Linux systems that do not use the newer threading model. For those systems, you can use a technique like the one described here.