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
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Logfile name should be created dynamically based on the network if I create a network testnet-sync then the log file should be lisk-testnet-sync.log or we can create separate log directory specific to network like logs/testnet-sync/lisk.log, either of the approaches should be good.
This way if a user is running multiple node from same code base at same place just by having custom network configuration then the logs will be created dynamically based on the network rather than changing the log file name in the custom network config file.
Actual behavior
Currently, when we start a network with parameter testnet-sync, we need to specify explicitly the log file name for custom log file name.
Which version(s) does this affect? (Environment, OS, etc...)
The text was updated successfully, but these errors were encountered:
Expected behavior
Logfile name should be created dynamically based on the network if I create a network
testnet-sync
then the log file should belisk-testnet-sync.log
or we can create separate log directory specific to network likelogs/testnet-sync/lisk.log
, either of the approaches should be good.This way if a user is running multiple node from same code base at same place just by having custom network configuration then the logs will be created dynamically based on the network rather than changing the log file name in the custom network config file.
Actual behavior
Currently, when we start a network with parameter
testnet-sync
, we need to specify explicitly the log file name for custom log file name.Which version(s) does this affect? (Environment, OS, etc...)
The text was updated successfully, but these errors were encountered: