On 15.12.2008 11:46, Nicolas Huillard wrote:
> The problem is that xineliboutput seems to use a single
> ~/.xine/config_xineliboutput config file, stored in the home directory
> of the vdr user, which is defined by /etc/passwd, which is the same on
> all clients...
You could mount different locati
On Thu, 18 Dec 2008, Nicolas Huillard wrote:
> I hope I'll be able to compile this patch before new year. Anyway, thank
> you very much for your efforts.
Well, I committed the patch already into CVS as I find it quite useful
while messing up e.g. with Xine's decoder priorities.
BR,
--
rofa
___
Rolf Ahrenberg a écrit :
> On Mon, 15 Dec 2008, Nicolas Huillard wrote:
>> Is there a way to tell xineliboutput which file to use ? Like adding a
>> command-line param "--config=~/.xine/config_xineliboutput.$(hostname)"
>
> The attached patch should implement this - no guarantees.
I hope I'll be
On Mon, 15 Dec 2008, Nicolas Huillard wrote:
Is there a way to tell xineliboutput which file to use ? Like adding a
command-line param "--config=~/.xine/config_xineliboutput.$(hostname)"
The attached patch should implement this - no guarantees.
BR,
--
rofa
xineliboutput-cvs-configfile.patch.
Hi,
I'm using xineliboutput on 3 VDR clients, sharing the same NFS root FS.
All clients are a bit different, and I solved most of the issues with a
separate VDR config dir for each client, basically running "/usr/bin/vdr
-c /var/lib/vdr.$(hostname) ...".
The problem is that xineliboutput seems
