Running As Service Under XP: Caveats?

[PeteCress]

I'm putting SageTV on an XP box where the intended use is tb run 24-7 or close to it.

i.e. When XP boots, I want SageTV to start and keep running until XP quits.

I'm thinking I won't see the SageTV window all the time and therefore will be less inclined to accidentally close it instead of minimizing it - thus shutting down Sage.

Any gotchas lurking here?

[stanger89]

That's how I've run it since V2 or so, well technically it was on Server 2003 until I rebuilt with XP recently.

[GKusnick]

Two things that usually trip people up when running as a service for the first time:

1. Services can't access mapped drive letters. Use UNC paths for your network import directories.

2. The default LocalSystem user can't access the network. (That's why it's called LocalSystem.) Configure the service to log in as a real user with appropriate permissions to access your network directories.

[PeteCress]

Originally Posted by GKusnick

2. The default LocalSystem user can't access the network. (That's why it's called LocalSystem.) Configure the service to log in as a real user with appropriate permissions to access your network directories.

Thanks. I think that was tripping me up.