FreeBSD: Socket Interface detach kills main process

[sofax222]

I have a problem about "Socket Interface" mode

I run openkore with "Socket Interface" mode in background on FreeBSD v8.1 (AMD64).

And then, run the src/Interface/attach-to-console.pl to moniter the background openkore process.
When I keyin the "detach" command to exit the moniter client (attach-to-console.pl).
Sometimes, "Sometimes" not "Always", the main openkore process in background is down (not quit) in the same time.

I don't know which programs I need to trace ?

[sofax222]

Well, there seems to be nobody to run openkore in background mode !

[EternalHarvest]

Used it, haven't noticed a problem like that.

[sofax222]

Used it, haven't noticed a problem like that.

I think the "detach" comand should exit the monitor provess only.
But in my scenario, the main opnekore process is down with the exit of the monitor process after the "detach" comand.

So, my question is not the "down" of main opnekore process.
My question is that the main opnekore process (running background) how to handle the "detach" command what I keyin in monitor provess (src/Interface/attach-to-console.pl) ?
That is how to trace the main opnekore process after the "detach" comand in the monitor process.

[EternalHarvest]

My question is that the main opnekore process (running background) how to handle the "detach" command what I keyin in monitor provess (src/Interface/attach-to-console.pl) ?
That is how to trace the main opnekore process after the "detach" comand in the monitor process.

"detach" is handled entirely by monitor process.
If main process is down due to some error in OpenKore it usually saves a report into errors.txt. If you want to inspect actual output, run it with Socket interface without putting into background (with something like screen if you need to detach from it anyway).

[sofax222]

"detach" is handled entirely by monitor process.
If main process is down due to some error in OpenKore it usually saves a report into errors.txt. If you want to inspect actual output, run it with Socket interface without putting into background (with something like screen if you need to detach from it anyway).

Yes, it is true that openkore will save the error message into errors.txt, if the main process have some thing wrong.
1. I could run the main process for all day long, even days.
2. The main process is down with the "detach" command on minitor process.
3. I find nothing in errors.txt (even it is not exist), when the main process down in the "detach" command of minitor process.