Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pruneancient command line argument flag vs config.toml flag #2003

Closed
zhk101 opened this issue Nov 26, 2023 · 1 comment
Closed

pruneancient command line argument flag vs config.toml flag #2003

zhk101 opened this issue Nov 26, 2023 · 1 comment

Comments

@zhk101
Copy link

zhk101 commented 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?

@zhk101 zhk101 changed the title pruneancient command flag vs config.toml flag (eg: pruneancient) pruneancient command flag vs config.toml flag Nov 26, 2023
@zhk101 zhk101 changed the title pruneancient command flag vs config.toml flag pruneancient command line argument flag vs config.toml flag Nov 26, 2023
@CocoStarZ
Copy link
Collaborator

Please use this tag in command line not config file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants