[
https://issues.apache.org/jira/browse/DAEMON-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mladen Turk closed DAEMON-57.
-----------------------------
Resolution: Won't Fix
Apart from academic, allowing spaces in service names makes no real value
and just complicates the parameter handling by requirement to properly quote
the arguments and service name processing.
There is service description which can be used to enter whatever description
needed.
> [daemon] prunsrv prohibits non-alphanumeric characters in service names
> -----------------------------------------------------------------------
>
> Key: DAEMON-57
> URL: https://issues.apache.org/jira/browse/DAEMON-57
> Project: Commons Daemon
> Issue Type: Bug
> Environment: Operating System: Windows 2000
> Platform: Other
> Reporter: StefanVogel
> Attachments: diff.txt, diff.txt, prunsrv.c, service.c
>
>
> On Windows, the Apache daemon prunsrv prohibits non-alphanumeric characters in
> the service name, for example blanks, while installing the service
> (//IS//<servicename>). Checking the service names on my machine and other
> peoples PCs show that there do exist services with blanks and numeric
> characters
> in the service name. So why is prunsrv prohibitting this?
> I have searched the web for any conventions regarding Windows servce names.
> The
> MSDN documentation for CreateService
> (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/createservice.asp)
> does only only forbid slash (/) and backslash (\). It defines the service name
> like this: "Pointer to a null-terminated string that specifies the name of the
> service to install. The maximum string length is 256 characters. The service
> control manager database preserves the case of the characters, but service
> name
> comparisons are always case insensitive. Forward-slash (/) and back-slash (\)
> are invalid service name characters."
> This should be fixed in service.c, __apxIsValidServiceName function by
> checking
> the service name length (max 256) and making sure there is no slash or
> backslash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
