I'd like to be able to use mythweb on a remote frontend so I can stream some shows and not tax the cpu on the backend.

When I try to access mythweb on the remote frontend, I get this:

Database Error

Can't connect to the database server. Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) [#2002]


Is there any way to configure mythweb to connect to a remote mysql server?

So basically the answer to my own question is to make my remote frontend a slave backend as well.

Are you actually talking about mythweb? Why run mythweb on a remote frontend with mythfrontend already working?

_________________
HP VL400 (PIII 866), Skystar2 2.6D, PVR350, Nvidia FX5200, 384MB, 200GB, KnoppMyth R5.5

The original goal was to be able to stream recordings from the remote frontend. The load on the backend was pretty high and streaming from it was causing allot of rebuffering. I assumed the rebuffering was caused by the high load of the backend (normaly com flagging) because I was getting the same results from watching a stream at a remote location as well as on the same local network. I figured I could use the frontend to do the streams.

The vlc process thats spawns when you start a stream eats up allot of system resources. My overall goal was to offload some of the work to a different machine. But now I see that I should still use mythweb on the master backend for two reasons. When I'm using mythweb on the frontend (with /myth mounted via nfs), I'm getting an error when vlc tries to play the file. I could have worked on this a little bit more, but then I found that since now there are two backends processing com flag jobs, the load on the master backend stays pretty low.

So I'm back accessing mythweb on the master backend with it doing the streams. I still have to rebuffer from time to time, but I believe some of those are being caused by network issues at the remote location where I'm viewing the streams from.