Prepackaged Windows binaries don't respect command-line flags when being installed as a service

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Running in Windows: "memcached.exe -d install -p 11213" followed by 
"memcached.exe -d start"
2.The service starts successfully, but it's still listening on the default port 
of 11211, not 11213.  This happens for all command-line parameters passed this 
way.
3.

What is the expected output? What do you see instead?
It would be expected that the service picks up the command-line parameters that 
the user has defined at installation time.

What version of the product are you using? On what operating system?
Windows, 32 or 64 bit

Please provide any additional information below.

Original issue reported on code.google.com by perryk...@gmail.com on 30 Jun 2010 at 6:09

[GoogleCodeExporter]

The -d option shouldn't be used to install memcached as a service (or used to 
start it as a windows service). -d means to start it as a daemon (detach from 
the tty etc). This change is already available in the engine branch.

If you want to run memcached as a "Windows service" one can use sc.exe to set 
it up (for more info see: http://support.microsoft.com/kb/251192/en-us )

Original comment by trond.no...@gmail.com on 4 Jul 2010 at 12:42

• Changed state: WontFix