Config variables not working properlly

[stronk-dev]

Config parameters often break, where even though they are defined in the launch script they do not get parsed correctly and use their default value instead. Changing the order of the parameters or using a = instead of a often fixes the issue, which causes confusion for new O's coming in:

• EG, John Obelish had to move their monitor flag in order to get it to work
• Organic-node has -autoAdjustPrice=false and -pricePerUnit=1199 but didn't receive any work since it was adjusting above 1200 (pricePerUnit is now set to 1099 and he is receiving work again)
• Another instance of the config variables not being parsed correctly

There have been plenty of other instances where over the past few months, maybe we can add some more verbosity over what config variables it has read or what values it is using?

[cyberj0g]

I think, it's a good idea to echo customized (because full list is too large) config values after livepeer start. WDYT?

[stronk-dev]

Yeah that sounds like a good first step, maybe we can also echo the full launch command on boot? So far I've only seen these kind of issues pop up with command line flags and not with with environment variables or config files

[thomshutt]

Not sure how easy this would be given we're using the golang flags package, but maybe printing all non-default flags could be a good subset?

[thomshutt]

Just realised that's what you meant by customized @cyberj0g 🤦 In that case, sounds good to me!