Igor Pechtchanski wrote:
Or perhaps you're reading it wrong. I read it as cygrunsrv will stick these environment variables into the environment of the process that it starts. Of course starting of cygrunsrv will also require access to cygwin1.dll and if that is not in your Windows System Environment Variable PATH (i.e. where the services pick up their environment variable PATH - before you log in) then cygrunsrv will fail too.Randall,An excerpt from "cygrunsrv --help" below -e, --env <VAR=VALUE> Optional environment strings which are added to the environment when service is started. You can add up to 255 environment strings using the `--env' option. Note: /bin is always added to $PATH to allow all started applications to find at least cygwin1.dll. shows that you shouldn't really need to add c:\cygwin\bin to your system path (if one uses cygrunsrv, that is). If that is not the case, then it's a bug in cygrunsrv (or an error in documentation). Igor
You see the way I see it cygrunsrv starts then forks the "service" you configured with it. Of course this now brings up the question of why doesn't cygrunsrv "exec" the service so that you don't see extra cygrunsrv processes in Task Manager. Perhaps the answer is that then it can't stuff the child's environment with these --env parms.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
