You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was under the impression that all the flags that can be passed via command line arguments to geth can be instead set in the config.toml
I was having the same issues that were fixed by #1986 but having the PruneAncientData = true in config.tml did nothing.
Instead I had to add the --pruneancient=true command line argument and the node started working fine with the latest bnb48club fast snapshot.
My question essentially is if this is expected behaviour and if it is, if there are other flags that behaves the same?
The text was updated successfully, but these errors were encountered:
zhk101
changed the title
pruneancient command flag vs config.toml flag (eg: pruneancient)
pruneancient command flag vs config.toml flag
Nov 26, 2023
zhk101
changed the title
pruneancient command flag vs config.toml flag
pruneancient command line argument flag vs config.toml flag
Nov 26, 2023
I was under the impression that all the flags that can be passed via command line arguments to geth can be instead set in the config.toml
I was having the same issues that were fixed by #1986 but having the
PruneAncientData = true
in config.tml did nothing.Instead I had to add the --pruneancient=true command line argument and the node started working fine with the latest bnb48club fast snapshot.
My question essentially is if this is expected behaviour and if it is, if there are other flags that behaves the same?
The text was updated successfully, but these errors were encountered: