e3d45eda1e
## Issue Addressed N/A ## Proposed Changes Earlier, to log to a file, the only options were to redirect stdout/stderr to a file or use json logging. Redirecting to stdout/stderr works well but causes issues with mistakenly overwriting the file instead of appending which has resulted in loss of precious logs on multiple occasions for me. Json logging creates a timestamped backup of the file if it already exists, but the json format itself is hugely annoying. This PR modifies the `--logfile` option to log as it does in the terminal to a logfile. |
||
|---|---|---|
| .. | ||
| account_utils | ||
| clap_utils | ||
| compare_fields | ||
| compare_fields_derive | ||
| deposit_contract | ||
| eth2_config | ||
| eth2_interop_keypairs | ||
| eth2_testnet_config | ||
| eth2_wallet_manager | ||
| hashset_delay | ||
| lighthouse_metrics | ||
| lighthouse_version | ||
| logging | ||
| remote_beacon_node | ||
| rest_types | ||
| slot_clock | ||
| test_random_derive | ||
| validator_dir | ||
| README.md | ||
eth2
Common crates containing eth2-specific logic.