Notification commands: Max outstanding throttling and ignore during reindex/rescan. #6031

During a reindex bitcoind launched hundreds of shells, crippling the server and getting the hosting company involved. Please implement throttling and add a filter to prevent calls when working with historical data.

... and that's one of the reasons why notification through running a shell command is a bad idea. If we'd use a socket based approach, this would be much less problematic.

Which kind of notification is the problem here? It's already tried to mitigate this, by only calling the block notifications when not IsInitialBlockDownload. This isn't the case for wallet notifications I think.

There is at least one reason anything is a bad idea, just because you've found it doesn't make you a super hero or anything, and that goes for whatever your suggestion is as well. This is why I'm attempting to do whatever it is I asked about doing and am blowing your thoughtless idea off with this canned response.

There is a socket RPC already and if you'd use the P2P socket you could get exactly what you're asking for. Though it'd take a moment to add an option to send notifications to a fifo.

I've both wallet and block running the same script, run-parts.