Installing Placeshifter on server?

[Ryand833]

I've been having a problem with SageTV for a while where if I load the UI up on my server, it will just peg the CPU at 100% and lock the whole system up.

Since it's a headless machine, I don't really NEED it to work since it runs as a service, but when I'm VNC/RDP'd into the system to do some work, I'd like to be able to fire up the UI and check settings/etc.

Since I can't load the SageTV UI directly on the system, what would happen if I install Placeshifter on the server itself?

Would this mess anything up with my Sage server installation?

[GKusnick]

Why not just run Placeshifter locally on the machine where you're sitting? If you can RDP into the server, you can Placeshift in, and do pretty much anything you could have done with a local UI running on the server.

[Ryand833]

Well, a lot of the times I'm outside the network completely, so I'm RDP'd directly into the sage server from (for instance, my machine at work).

It's not that much of an inconvenience to RDP to another box to get in through placeshifter, but it would be nice to be able to do it on the sage box itself.

Maybe I should forget placeshifter and try to figure out why it hits the CPU so hard when I load it...

[GKusnick]

To answer the original question, yes, you can install Placeshifter on the server. But I'm still not seeing how this is better than running Placeshifter on your work machine and using it it instead of RDP to connect to your server over the Internet, which is precisely what Placeshifter is designed to do.

You can also carry a Placeshifter installation on a USB stick and run it directly from the stick on any Windows machine without having to install it on that machine.