Atm, the CLI output will show "geth started" + "node is running"
But it is based on just having a successful call to geth binary. If geth exits 0.5sec later for some config error, user won't know and will think the node is up while it is not.
This is simply to change this message which can be wrong.
Atm, the CLI output will show "geth started" + "node is running" But it is based on just having a successful call to geth binary. If geth exits 0.5sec later for some config error, user won't know and will think the node is up while it is not.
This is simply to change this message which can be wrong.
Current:
-> Misleading log messages.