-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any way to disable attrib
behaviour?
#7
Comments
Hello,
will just work. Thanks for the detailled description of problem, it was very useful to understand your need. |
I'm building 0.29b right now, with the fix. I tested it well with tool
|
That's great, I'll check it. P.S. Why binary is so big compared to xmrig, which is around 1MB unpacked? |
Because the binary contains literally hundreds of versions of the CN implementation, in assembly. With or without AES, SSE4, AVX, for P4, for Athlon, for Core2... Without or without cache, dual-thread, simple, double up to hexa hash... for all CN variations (they are 10 now). |
@jceminer Hello, Also, you referenced windows-kill.exe, but I can't file anything like this file. Where to find it? |
@jceminer It's where the magic happens. Started script from cmd (to be precise, powershell), it catches all input, even if I don't forward it to jce. There's no that magic on xmrig or xmr-stak. When I stop a whole script, JCE stops too, but not from kill() function. That's how you can reproduce that - create
Even if stdin is holed, it anyway catches the input. Watch up for UPDATE: If I kill a whole tree, it works fine. Like |
it forwards, but the Posix signals, not the Win32 kill, take a look at this Posix signal sender |
Ok, no problem with killing process. Let's think another scenario:
I can make process detached, but that makes another problem. In that case empty cmd window appears with "kernel64.exe" title. If I close that window, nothing happens and attrib.exe hangs in process list. Is it possible for you to forward win32 signals? I was thinking about killing all attrib.exe processes to terminate jce, what do you think about it? Is that safe to use? |
|
It should be fixed in the 0.31d GPU. To be backported to CPU version. |
Reported to work by Quake4 who faced the same issue. closed. |
Hi,
I'm trying to run/stop this miner from outside. I'm using Node.JS but I pretty sure it's not related to Node.JS.
I spawn it:
It works fine and I see CPU usage in Task Manager.
![image](https://user-images.githubusercontent.com/17164985/40806077-756edcdc-6531-11e8-9b47-37e338df0ece.png)
I stop it:
But it doesn't stop, because miner creates separated process.
![image](https://user-images.githubusercontent.com/17164985/40806109-8857b0c6-6531-11e8-81ae-b7e7671df06c.png)
Is there any way to disable that trick or would you recommend something else?
P.S. I even tried
this.daemon!.stdin.write('q');
, It doesn't work too (but stdout reads fine!). I can't figure out how did you do that; I have never seen that before.Thanks in advance!
The text was updated successfully, but these errors were encountered: