Service mode VS Standalone?

[dpackham]

what are the benifits or not of running SageTV on a standalone windows XP system in service mode? against just running the service without the service?

The computer is dedicated to SageTV and only serves one MVP and web interface.

I know that I can stop the main GUI with service mode. but is that it? I also know that the web remote does not work in service mode. is there a list that compairs the two modes?

Thanks
Dave P

[Fluffdaddy]

Good questions

I have never used service mode. I always wanted to know the advantages in doing so but never thought to ask.

server feeding
two MVP's
one PC client

[matt91]

If by web remote you mean the remote via Nielms www server, it works in service mode.

[GKusnick]

Originally Posted by dpackham

against just running the service without the service?

I have no idea what you mean by that, but off the top of my head here are some differences between service and non-service modes.

• If the UI crashes in non-service mode, so does the recording engine. In service mode, UI crashes don't affect the recording engine, so you can experiment freely with UI mods and such with much less risk of losing recordings. (This is probably the main reason for using service mode in my opinion.)

• If the service does crash, it can restart itself automatically. That's harder to do in non-service mode without looping batch files or something similar.

• Services start before you log in to Windows. So if your computer reboots for any reason, SageTVService can start recording right away, before you log in.

• Services can't access mapped drive letters. So if you have recording or import directories on other servers, you'll need to use UNC paths to access them from SageTVService.

[KrisAcker]

Originally Posted by GKusnick

If the service does crash, it can restart itself automatically. That's harder to do in non-service mode without looping batch files or something similar.

If you configure the properties of the service in the Windows interface instead of the Sage interface, you can tell Windows what to do on the "First failure", "Second failure" and "Subsequent failures". As you're talking about a dedicated machine, you could even select "Restart the computer" for the last one.

[dpackham]

Cool thanks. when its running in service mode i get this error when I try to use the web remote

UI Context: "SAGETV_PROCESS_LOCAL_UI" is not active:
Webserver is running in SageTV Service - no remote control possible
use: /sage/SageCommand?command=<command>&context=<context>

both the frontend and backend are running.

Thanks all for the service info. I think ill keep running in service mode

Dave P

[KrisAcker]

Originally Posted by dpackham

Cool thanks. when its running in service mode i get this error when I try to use the web remote

UI Context: "SAGETV_PROCESS_LOCAL_UI" is not active:
Webserver is running in SageTV Service - no remote control possible
use: /sage/SageCommand?command=<command>&context=<context>

both the frontend and backend are running.

Thanks all for the service info. I think ill keep running in service mode

Dave P

That sounds like you're running the webserver in the service instance. For the webremote to have access to the client, it has to run in the client instance. To do this, you have to add the load_at_startup_runnable_classes=net.sf.sageplugins.webserver.StartServer line to the SageClient.properties file instead of the Sage.properties file.