[
https://issues.apache.org/jira/browse/DAEMON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390455#comment-17390455
]
Mark Thomas commented on DAEMON-411:
------------------------------------
Breaks which version of Tomcat, on which version of Windows, how? I haven't
noticed any issues in my local testing. Also this patch has been in place for
2+ years and I don't recall Tomcat users reporting this as an issue.
I would very strongly against changing the default user back to LocalSystem
because of the security implications.
> Services can't be installed as Type=Interactive anymore
> -------------------------------------------------------
>
> Key: DAEMON-411
> URL: https://issues.apache.org/jira/browse/DAEMON-411
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.2.0
> Environment: openjdk version "1.8.0_222"
> OpenJDK Runtime Environment (Zulu 8.40.0.25-CA-win64) (build 1.8.0_222-b10)
> OpenJDK 64-Bit Server VM (Zulu 8.40.0.25-CA-win64) (build 25.222-b10, mixed
> mode)
> Tested on Windows 10 1607 and Windows 7 7601.
> Reporter: Markus Adelsberger
> Priority: Major
> Labels: windows
> Fix For: 1.2.3
>
> Attachments: prunsrv.png
>
>
> Installing a service with the parameter --Type=interactive no longer works.
> prunsrv.exe outputs:
> {code:java}
> prunsrv.exe //IS//MyService
> --Install="C:\service\commons-daemon-1.2.2-bin\windows\amd64\prunsrv.exe"
> --Type=interactive --ServiceUser="LocalSystem"
> The parameter is incorrect.
> Failed to install service.{code}
> No other log is output, even with Debug level. As a workaround the service
> can be installed without the type interactive and then updated to use the
> flag.
> The same call still worked in 1.1.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
