interesting
/
go-ethereum
mirror of https://github.com/ethereum/go-ethereum.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

doc: fix typo and command in geth documentation (#26577) 

This PR fixes a typo and an invalid command in doc.

Co-authored-by: Florian Sey <florian.sey@neofacto.com>
This commit is contained in:
Florian Sey 2023-01-31 03:06:21 +01:00 committed by GitHub
parent c9948319c1
commit 155738f30c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/fundamentals/logs.md
View File

@ -5,7 +5,7 @@ description: Geth's log messages explained
A Geth node continually reports messages to the console allowing users to monitor Geth's current status in real-time. The logs indicate when Geth is running normally and indicates when some attention is required. However, reading these logs can be difficult for new users. This page will help to interpret the log messages to better understand what Geth is doing.
Note that there are a large number of log messages covering a wide range of possible scenarios for a Geth node. This page will only address a subset of commonly seen messages. For more, see the [Geth GitHub](https://github.com/ethereum/go-ethereum), [Discord](https://discord.gg/WHNkYDsAKU) or search on [ethereum.stackexchange](https://ethereum.stackexchange.com/). Log messages are usually sufficiently self-descrining that they do not require additional explanation.
Note that there are a large number of log messages covering a wide range of possible scenarios for a Geth node. This page will only address a subset of commonly seen messages. For more, see the [Geth GitHub](https://github.com/ethereum/go-ethereum), [Discord](https://discord.gg/WHNkYDsAKU) or search on [ethereum.stackexchange](https://ethereum.stackexchange.com/). Log messages are usually sufficiently self-describing that they do not require additional explanation.
## Configuring log messages {#configuring-log-messages}

2
docs/fundamentals/private-network.md
View File

@ -162,7 +162,7 @@ geth --datadir data --networkid 15 --nat extip:172.16.254.4
The 'node record' of the bootnode can be extracted using the JS console:
```sh
geth attach data/geth.ipc --exec admin.nodeInfo.enr
geth attach --exec admin.nodeInfo.enr data/geth.ipc
```
This command should print a base64 string such as the following example. Other nodes will use the information contained in the bootstrap node record to connect to the peer-to-peer network.