[network] disable = true in config file is ignored

[lgpawel]

Here's a console log:

$ cat config.toml 
[network]
disable = true
$ parity --config config.toml 
Loading config file from config.toml
2017-03-01 12:23:57 UTC Starting Parity/v1.6.0-unstable-b13a446d8-20170227/x86_64-linux-gnu/rustc1.15.1
2017-03-01 12:23:57 UTC State DB configuration: fast
2017-03-01 12:23:57 UTC Operating mode: active
2017-03-01 12:23:57 UTC Configured for Frontier/Homestead using Ethash engine
2017-03-01 12:23:57 UTC Updated conversion rate to Ξ1 = US$15.83 (7520380000 wei/gas)
2017-03-01 12:24:03 UTC Public node URL: enode://cd08db004bfe13cae04aedb15ebe8687ac1918c9f942d7a52584960be1f34000c5daeb414304fc6c3f541947d1437a1a43ed7816a7ec9d71e2c6c5f000004f5c@192.168.3.197:30303
2017-03-01 12:24:12 UTC Syncing #2423022 309b…ebbd     5 blk/s   50 tx/s   1 Mgas/s    834+ 5966 Qed  #2429831    8/ 8/25 peers   284 MiB db  161 KiB chain   38 MiB queue    3 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
^C2017-03-01 12:24:13 UTC Finishing work, please wait...

Operating mode stays active (as opposed to when Parity is run with --mode offline) and accordingly connections are established, blocks synced etc.

[tomusdrw]

Seems that the CLI flag was deprecated/removed, but that option was not removed from config files.

Currently it should be done via --mode offline as you've posted.

[lgpawel]

And via config file? [parity] mode = "offline"?

[tomusdrw]

Yup, that seems right.