Configuration / config broken - does not work - does not load config
Starting the 3.9.1-linux miner like so;
```bash
/opt/nanominer/nanominer /opt/nanominer/config.ini
```

config.ini file:
```ini
; nanominer configuration file.
; LINES STARTING WITH ";" ARE COMMENTS WHICH ARE NOT PARSED BY MINER.
; Full configuration file description and examples can be
; found in README document.
watchdog=0
noLog=1
checkForUpdates=0
autoUpdate=0
noColor=1
```

output (in colour ofcourse):
```
                                   _                 
 _ __   __ _ _ __   ___  _ __ ___ (_)_ __   ___ _ __ 
| '_ \ / _` | '_ \ / _ \| '_ ` _ \| | '_ \ / _ \ '__|
| | | | (_| | | | | (_) | | | | | | | | | |  __/ |   
|_| |_|\__,_|_| |_|\___/|_| |_| |_|_|_| |_|\___|_|   

Version 3.9.1-linux
2024-Jun-11 23:06:02: Started EthMan server on port 3333 without a password (read-only mode).
2024-Jun-11 23:06:02: Started web interface on port 9090 without a password.
2024-Jun-11 23:06:02: NVIDIA driver version: 535.161.08 (12.2)
2024-Jun-11 23:06:02: Could not find nvrtc library!
Single device detected
GPU 0 PCI 0a:00.0, Platform: CUDA, Name: NVIDIA GeForce RTX 2080 Ti, 11003 MB available
-------------------Ethash:------------------
Currency: Ethereum Classic
Wallet: xxxx
Rig name: xxxx
Email was not set.
Hashrate threshold to restart miner is not set
Number of rejected shares per hour to restart miner is not set
Added pool: etc-eu1.nanopool.org:10143
Added pool: etc-eu2.nanopool.org:10143
Added pool: etc-us-east1.nanopool.org:10143
Added pool: etc-us-west1.nanopool.org:10143
Added pool: etc-asia1.nanopool.org:10143
Added pool: etc-jp1.nanopool.org:10143
Added pool: etc-au1.nanopool.org:10143
Auto pool sorting is enabled
Using all GPU devices
Memory tweak: 1
-------------Common parameters:-------------
Log path: ./logs/
Log is written to file
GPU watchdog is enabled
Never calling reboot.sh (always restarting the miner in case of errors). 
```


Also, when started in a docker container without `-it` there are buffer issues with the output, and the SIGTERM signal doesn't seem to be handled properly