quiet_mode in proxychains.conf does not work about proxychains-ng

[fyangami]

same issue too.

[TimeRainStarSky]

same issue too.

[rofl0r]

it's a difficult problem. at the point the config is parsed, these messages were already printed. i'd have to implement some sort of caching (involves memory allocation) and postpone printing of the output until config parsing is done. memory allocation in a hook library can lead to all sorts of issues in multithreaded/multiprocess (fork()ing) apps, that's why most (or all, in case the threaded resolver is disabled) memory is statically allocated. therefore my leaning is to obsolete the config option and recommend instead the use of -q or setting the environment variable PROXYCHAINS_QUIET_MODE=1 instead. even though the output of proxychains may appear annyoing to you, it's the only way to make sure the program is properly hooked.