Changing the status is that this is still a bug even if the reload won't
be fixed.
If reloading of configuration is not to be supported, then the following bugs
should be fixed:
(1) Running "/etc/init.d/squid" prints:
Usage: /etc/init.d/squid {start|stop|reload|force-reload|restart}
I should not print "reload" and "force-reload" if on-the-fly configuration
reloading is not supported
(2) Running "/etc/init.d/squid reload" says it successfully reloaded the
configuration and exits with 0 exit code:
sudo /etc/init.d/squid reload
* Reloading Squid configuration files
...done.
~$ echo $?
0
(3) Running "/etc/init.d/squid force-reload" says it successfully reloaded the
configuration and exits with 0 exit code:
sudo /etc/init.d/squid force-reload
* Reloading Squid configuration files
...done.
~$ echo $?
0
So either (a) squid has to reload configuration for reload & force-
reload or (b) the reload & force-reload should not be presented as
options, and the init.d script should print an error to std-err and
return with a non-zero exit code. But either way this is a bug that
ought to be fixed.
** Changed in: squid (Ubuntu)
Status: Won't Fix => New
--
squid must be restarted after configuration change
https://bugs.launchpad.net/bugs/204474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
