On Thu, Dec 4, 2008 at 7:28 AM, William A. Rowe, Jr. <wrowe@xxxxxxxxxxxxx> wrote: > Vasanth Kumar ravi wrote: >> Well the problem is here is the root access. >> I am an application administrator and the root passwd is owned by the >> system administrator team. >> since this a dev setup, i got the root passwd but for production they >> would not give it. >> so either I have to go for a port forward in production or ask the >> system admin to manage the apache. > > Or you ask for sudo access to a script which kicks off, starts and stops > apache. This requires you to have nobody's password except your own. Anybody who has the privileges to edit the apache config file and to start and stop apache using sudo can become root. So if system administrators don't want you to have root access to should be prepared to manage apache themselves. Basically the best practise is to develop your apache config on a dev server, and delvier the result to the production server's admin with instructions on how to install and manage it. Krist -- krist.vanbesien@xxxxxxxxx krist@xxxxxxxxxxxxx Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|