https://issues.apache.org/bugzilla/show_bug.cgi?id=41564
--- Comment #7 from Will Rowe <wr...@apache.org> 2009-05-26 12:09:56 PST ---
Reviewing further, I see that service.bat is invoked by the user after install,
and not by the nullsoft installer.
Bogdan is correct in comment #4, however it seems more of a documentation
issue.
If the user will be modifying the system environment from a command prompt,
they
must do so from an admin cmd.exe shell, and there are only two ways to have
one;
1. right click on your cmd.exe ("Command Prompt" icon) and choose "Run as
Administrator".
2. from the shell, invoke
runas user:administrator "cmd.exe /k"
which will open a new admin-privileged shell.
There is no way to associate service.bat with elevation via a .manifest or
otherwise. Only actual .exe's can be associated. There is a code elevation
model for invoking programs as admin, see the am_RespawnAsUserAdmin()
implementation within the ApacheMonitor.exe app (which doesn't want to run-as
admin until it is absolutely required, and certainly not hang for a permission
change each time the user logs in!)
http://svn.apache.org/repos/asf/httpd/httpd/trunk/support/win32/ApacheMonitor.c
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
