Slush,
holy war and associated FUD aside

what attracted me to stratum was low bandwidth minimal pool software which is giving miners great results re stales and bandwidth savings (especially with VarDiff), where is the demand from miners to include this extra "functionality"- I see only 1 individual calling for this
Leave the author of GBT to fix his software and you focus on stratum - rather than changing stratum to suit him
Please do not bog down stratum with extra unneeded and unwanted code - if miners don't trust the pool they are mining on to do the right thing - why do they mine there at all?

Making a BIP for this is also a diversionary measure to waste your time, please, take a moment, step back and consider what is actually needed and will improve the protocol you have designed
Thanks for your time and effort creating a viable mining protocol and sharing it with us all
Graeme

Ok, let's focus to important things and don't solve something, what's not a problem. I'm going to disable get_transactions() on my pool, at least until Luke stops abusing it in holyminer.

Okay, stupid question here. I'm sure there is a simple answer but I'm not pulling it right now. Here is my problem:

I'm running BAMT on a headless, caseless setup. I'm trying to install Stratum, I have it installed and working. I have two problems though:

1. Since I'm headless, if I open a terminal window and putty in to the BAMT box I need to keep the computer I am logging in from turned on and the terminal window open, or Stratum stops. I know I can probably use nohup to get around this but since it automatically redirects to a log, and BAMT runs off of a flash drive, I need to figure a way for it to not be logging or I'm going to wear out my flashdrive mighty quickly (not to mention filling it to overflow first probably).

2. Same issue, Bamt, headless, caseless, etc... I want to set Stratum to start in the startup sequence so if I have to power down the BAMT box Stratum automatically starts up before the mining software does. I know where to put it, in theory, to do so but I need the same issue resolved. If the actual solution to my question #1 won't work in a startup sequence, then I need to know how to do the same thing in the startup sequence.

I keep my BAMT box on 24/7 except for reboots. I do not keep the windows machine I am using to log into the BAMT box on 24/7 so I'm trying to figure out how to resolve these issues so I can use Stratum all the time. Sorry if they are newbieish questions but I haven't been doing much with linux in more than a decade (except minimal experimentation to get BAMT going).

Thank you for any help in advance.
Thralen

Thanks Graet, that looks like it'll be a solution for problem #1. There probably isn't any way to integrate that to problem #2 though, is there? Sorry to be a pain and as I said, thank you for the solution. That should at least let me be shutting my windows box off overnight. So long as I don't have an unexpected reboot on the BAMT box it'll work and I can always set it to roll over to non-Stratum proxy mining if it does reboot on me.

Thralen

my bad, I rarely detach
I'll edit post - cheers

Put something like this toetc/rc.local

Then you can attach console by "screen -x proxy" and detach it (without stopping it) by Ctrl-a,d (double combo)

hello Slush

is it very stupid idea ? to add feature to your stratum mining_proxy.exe  additional feature to save stats data per worker and per block to local computer ?

for example "mining_proxy -f" means store block stats data to file to local comp where mining_proxy running

i think a many files will better than 1 file, the file per block (with the worker shares ) will reasonable ?
new block started - new file created? block found - file closed.

csv (or json) format for the stored data will great

Strange, I never had segfault on any of my machines (including ARM boxes etc). Do you have some unusual machine configuration? Are other applications stable?

That will work, because crash of the proxy won't affect the watchdog itself.