No verbose on centos 7
chichi13 opened this issue · 3 comments
Hello !
I have a problem with the verbose of siege on my centos 7 machine. I have no verbose, even if I'm putting the '-v' flag.
Here is the configuration :
siege -C
CURRENT SIEGE CONFIGURATION
Mozilla/5.0 (redhat-x86_64-linux-gnu) Siege/4.0.5
Edit the resource file to change the settings.
----------------------------------------------
version: 4.0.5
verbose: false
color: true
quiet: true
debug: false
protocol: HTTP/1.1
HTML parser: enabled
get method: HEAD
connection: close
concurrent users: 25
time to run: n/a
repetitions: n/a
socket timeout: 30
cache enabled: false
accept-encoding: gzip, deflate
delay: 0.000 sec
internet simulation: false
benchmark mode: false
failures until abort: 1024
named URL: none
URLs file: /etc/siege/urls.txt
thread limit: 5000
logging: false
log file: /home/exploit_probance/siege.log
resource file: /home/exploit_probance/.siege/siege.conf
timestamped output: false
comma separated output: false
allow redirects: true
allow zero byte data: true
allow chunked encoding: true
upload unique files: true
json output: true
no-follow:
- ad.doubleclick.net
- pagead2.googlesyndication.com
- ads.pubsqrd.com
- ib.adnxs.com
proxy auth:
www auth:
When I'm looking at the siege.conf the verbose is at 'True' :
cat .siege/siege.conf | grep 'verbose'
# ex: verbose = true|false
verbose = true
The consequence of this problem is that I don't see any messages when I execute siege :
siege -r1 -c1 -H 'Content-Type: application/x-www-form-urlencoded' 'http://*.*.*.*:8080/map POST https://www.google.com/search?q=cat' -v
{ "transactions": 1,
"availability": 100.00,
"elapsed_time": 0.01,
"data_transferred": 0.00,
"response_time": 0.01,
"transaction_rate": 100.00,
"throughput": 0.00,
"concurrency": 1.00,
"successful_transactions": 1,
"failed_transactions": 0,
"longest_transaction": 0.01,
"shortest_transaction": 0.01
}
With or without the -v flag, it's the same :'(
Thanks in advance.
It appears that the last feature 'json output' is automatically to True and cancel the flag '-v' or the configuration 'verbose=true'
So, to resolve the 'problem', you need to put the 'json_output=false'
I let you decide if this is a bug or not.
Hi, I was able to reproduce this issue with the default configuration file:
Since the default configuration file has json_output set to true
( siegerc.in : https://github.com/JoeDog/siege/blob/master/doc/siegerc.in#L70 )
and the json_output monopolizes stdout, superceding verbose,
( init.c : https://github.com/JoeDog/siege/blob/master/src/init.c#L691-L696 )
I created a PR with a proposal to improve this:
#182