Quote from: guytechie on Today at 05:13:38 AM

Quote from: JayDDee on September 05, 2021, 04:22:23 PM

Quote from: guytechie on September 05, 2021, 02:34:51 PM

Quote from: doktor83 on September 03, 2021, 05:32:52 AM

Quote from: guytechie on September 02, 2021, 07:52:22 PM

Does this fix the miner from completely exiting out of a bash script? I'm still having this issue. Been using a different miner until this is fixed.

Can you try it in a script yourself to verify the behavior and debug to find out why this is happening though? I am not a developer so I have no idea how to find out why this happens.

Im not sure i can fix anything for you. Miner on SIGINT or SIGBREAK does a cleanup, shutdown and exits to shell, it's up to you what you do in your script after that.
Mining distros like Hiveos, Mmpos, etc have no issues with the shutdown procedure...

And you will prob. now say but other miners work normally [this is what people usually say].

I have no idea why it would be different for different miners (or any application). The application has no control over the script
that called it, all it can do is exit and let bash take over from there.

Are there any differences in the script or the bash environment. Are there any other differences in behaviour like console messages?

I don't know why it behaves this way either. It doesn't happen with other miners such as t-rex, ccminer, or even your own cpuminer-opt.

I don't know much about Linux as I'm just starting to learn it. I'm carrying a lot of command line experience from my DOS days.

Do you run the script as a user or with sudo?
In your script put set -x under $!/bin/bash start it from the terminal it shows you what happens with the script. Also instead of using xmrig-cpu (which is not actively maintained anymore) use xmrig https://github.com/xmrig as that is the latest official one.