Luke Kanies wrote: > > When 'apache2ctl status' is called against a server that does not have > the 'status.cgi' configured, it gets a 404 but then still exits with a 0 > exit code. While in some ways it could legitimately be said to have > verified that the server is at least running, it gives a false > impression via its exit code, one which is particularly frustrating with > automated tools.
Not sure how the exit code of "status" would ever be meaningful without also looking at the output, as lynx may have succeeded, but the status page could be telling you that your webserver's on fire. The whole point of "status" is the output, as far as I'm concerned. ... Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
