heddaz / serviceonset Goto Github PK

目前的做法是生成一个 ServiceOnset 服务管理所有程序。如果我用一个ServiceOnset.exe同时管理几个CMD程序，例如像下面这样的配置：
{
"enableLog": true,
"services": [
{
"name": "aaa",
"command": "aaa.exe"
},
{
"name": "bbb",
"command": "bbb.exe"
},
{
"name": "ccc",
"command": "ccc.exe"
}
]
}
如果现在 aaa应用有点小问题，我想重启一下aaa服务，就要重启ServiceOnset服务，这时ServiceOnset管理的 aaa,bbb,ccc,3个程序都会重启，感觉有点不太方便，能不能考虑把不同的程序生成不同的服务，这样可以单独管理，互不影响。比如aaa程序，根据他的 name 值，生成 aaa服务，bbb，ccc，同理。不知我的建议是否合理？

Because some apps init something in FORM_LOAD event.

Run different services with different accounts.

可以配置目录吗？我试了command加路径不行

Somehow , I changed the config file name. And when I try to start the serviceonset.exe service, windows tell me can't start this service because program didn't response in time. Maybe you just can't find the config file, but at least tell user what's happened and what do the program need to start.

It is a [session 0 isolation] problem on Win2008 or above.

Currently simply remove the "AllowWindow" parameter and added a Interop.cs for the preparation.

Refer to: http://www.cnblogs.com/therock/articles/2261371.html

全新安装了win10重新下了最新sos，和之前#4的问题一样，相对目录也失败

我试了一下，workingDirectory 参数好像不支持相对路径，能否考虑添加以 ServiceOnset.exe 或者 ServiceOnset.exe.json 为根的相对路径支持，因为我的cow是放在ServiceOnset目录下面一个子目录。如果我要换电脑，或者移动了ServiceOnset目录到其他位置，又得改workingDirectory 参数，如果使用相对路径的话，只要保持ServiceOnset目录内部结构不变，就不存在这个问题了。