I just installed Siege 3.1.4 on an Ubuntu 16.04 server with the prefix configured as my homedir, so by using:
./configure --prefix=/home/jan
It all went well and I got siege up and running. But at the end of a siege, it says:
LOG FILE: /usr/local/var/siege.log
You can disable this log file notification by editing
/home/jan/.siege/siege.conf and changing 'show-logfile' to false.
[error] unable to create log file: /usr/local/var/siege.log: No such file or directory
Since I'm running siege as my local user and Ubuntu doesn't have a var dir under /usr/local by default, it cannot write the log file.
But, the help text says:
-l, --log[=FILE] LOG to FILE. If FILE is not specified, the
default is used: PREFIX/var/siege.log
Obviously it's not using the PREFIX dir at all. It's going straight for /usr/local.
If I manually define the log file to be saved in my homedir it works just fine, but the help text doesn't match the default behaviour.
The cleanest solution would be to actually honour the PREFIX that was set during installation.
I just installed Siege 3.1.4 on an Ubuntu 16.04 server with the prefix configured as my homedir, so by using:
It all went well and I got siege up and running. But at the end of a siege, it says:
Since I'm running siege as my local user and Ubuntu doesn't have a var dir under /usr/local by default, it cannot write the log file. But, the help text says:
Obviously it's not using the PREFIX dir at all. It's going straight for
/usr/local. If I manually define the log file to be saved in my homedir it works just fine, but the help text doesn't match the default behaviour.The cleanest solution would be to actually honour the PREFIX that was set during installation.