What are our current options for creating userland services in reactos? We don't seem to have an svchost, so should I make my service a standalone exe for now?
Is anybody working on service support?
I have been wondering about what reactos will do also about services, processes, and servers being utilized when reactos becomes 100% compatible with MS Windows NT versions. I was wondering if ReactOS would consider taking a look at how BeOS protects these servers, services, and processes. For those of you that don't know if a sound server crashes in beos it is shutdown without crashing the system. This would greatly add productivity, functionality, and security to the ReactOS.
I think that reactos could also use something like a "swap partition" or method to write information to an encrypted volume to use for later it reactos crashes. I know that something like a "rapid restore" feature would greatly excite users so when ReactOS crashes it can be resumed without problems or loss of work.
ssss.... Micro$oft is watching... they 'll steal your ideas :o
On Tue, 8 Mar 2005 07:30:14 -0600, Rick Langschultz rlangschultz@cox.net wrote:
I have been wondering about what reactos will do also about services, processes, and servers being utilized when reactos becomes 100% compatible with MS Windows NT versions. I was wondering if ReactOS would consider taking a look at how BeOS protects these servers, services, and processes. For those of you that don't know if a sound server crashes in beos it is shutdown without crashing the system. This would greatly add productivity, functionality, and security to the ReactOS.
I think that reactos could also use something like a "swap partition" or method to write information to an encrypted volume to use for later it reactos crashes. I know that something like a "rapid restore" feature would greatly excite users so when ReactOS crashes it can be resumed without problems or loss of work.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
art yerkes wrote:
What are our current options for creating userland services in reactos?
Services.exe can start standalone services (.exe files) but controlling them is impossible because of missing RPC code in the service manager.
We don't seem to have an svchost, so should I make my service a standalone exe for now?
Yes! Eventlog and umpnpmgr are already working this way.
Is anybody working on service support?
I'm working on WIDL in order to implement the service control code in services.exe and advapi32.dll.
Btw, right now I don't have much time for hacking except for the weekends because I am attending a 6-month programming course. I hope to add the next feature to WIDL by the weekend.
Regards, Eric
On Tue, 08 Mar 2005 20:54:42 +0100 Eric Kohl eric.kohl@t-online.de wrote:
art yerkes wrote:
What are our current options for creating userland services in reactos?
Services.exe can start standalone services (.exe files) but controlling them is impossible because of missing RPC code in the service manager.
Ahh thanks, that's just what I was wondering. I'll use services.exe.