Klaus Schmidinger wrote:
>> i suggest the introduction of a new command line option to switch
>> off writing any epg data (implicitly switching off epg scan). this way
>> only the server vdr maintains the epg and the clients only read it.
>
> The clients would only read this once at program start.
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> > i suggest the introduction of a new command line option to switch
> > off writing any epg data (implicitly switching off epg scan). this
> > way only the server vdr maintains the epg and the clients only read
> > it.
> The clients would only read
On 11/04/07 11:09, Clemens Kirchgatterer wrote:
> Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
>> Each instance of VDR writes into epg.data without any locking or so.
>> If you set up more than one VDR that write to the same epg.data,
>> the last one writing it will "win", and if they write at t
Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
> Each instance of VDR writes into epg.data without any locking or so.
> If you set up more than one VDR that write to the same epg.data,
> the last one writing it will "win", and if they write at the same
> time, results may be undefined.
i suggest th
On 11/03/07 21:55, Clemens Kirchgatterer wrote:
> is it save to share one epg.data file between multiple vdrs over nfs?
> or should each client maintain its own copy?
Each instance of VDR writes into epg.data without any locking or so.
If you set up more than one VDR that write to the same epg.dat
is it save to share one epg.data file between multiple vdrs over nfs?
or should each client maintain its own copy?
thx ...
clemens
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
