Here is where I am with this bug. postinst calls /usr/share/wwwconfig-common/restart.sh, which itself calls /etc/init.d/apache2 restart.
If the restart fails with exit value != 0, the execution of the scripts stops, thus making postinst fail. If I replace /usr/share/wwwconfig-common/restart.sh by a single call to an external script which contains only a line "exit 1", postinst will fail; with "exit 0", it will work. I would think that if the external script exits with return value 1, /usr/share/wwwconfig-common/restart.sh would get this return value and continue its execution, but no, it never gets an opportunity to continue executing -- which means that postinst will not be able to continue executing, and it will look like it failed. I am maybe missing something simple here, but I have not been able to reproduce this behaviour outside of postinst -- everytime the external script exits with value 1, return.sh just continue executing normally. Any help ? There may be more questions about how w3c-markup-validator should restart (or maybe reload) the webserver, and what it should do if this fails, but this is not as urgent as the actual bug. Tell me if this is not quite clear -- it's pretty late here... Cheers, Frederic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
