Am 25.08.2013 12:30, schrieb Klaus Schmidinger:
> On 25.08.2013 12:23, Lars Hanisch wrote:
>> Hi,
>>
>> Am 20.08.2013 08:59, schrieb syrius...@no-log.org:
>>> Manuel Reimer writes:
>>>
Hello,
with event based init systems (in my case systemd) it seems to become
a big issue to s
On 25.08.2013 12:23, Lars Hanisch wrote:
Hi,
Am 20.08.2013 08:59, schrieb syrius...@no-log.org:
Manuel Reimer writes:
Hello,
with event based init systems (in my case systemd) it seems to become
a big issue to startup VDR.
If you install VDR on a SSD device, then startup gets *really*
fast
Hi,
Am 20.08.2013 08:59, schrieb syrius...@no-log.org:
> Manuel Reimer writes:
>
>> Hello,
>>
>> with event based init systems (in my case systemd) it seems to become
>> a big issue to startup VDR.
>>
>> If you install VDR on a SSD device, then startup gets *really*
>> fast. Sometimes that fast,
On Wed, Aug 21, 2013 at 2:40 AM, cedric.dew...@telfort.nl <
cedric.dew...@telfort.nl> wrote:
> I have 3 USB receivers. Sometimes my cat runs over the cables, and in some
> cases causes one receiver to be loose. I would like VDR to be able to start
> in that situation, and not wait until all adapte
This works for *one* system and only if the user manually sets the number of
adapters. How could this be done in a "automagic" way to allow users to just
plug the tuner and reboot?
I don't think you can automate that in a very reliable way, especially if
you're using usb dvb devices and/or de
On Tue, Aug 20, 2013 at 1:20 AM, Manuel Reimer wrote:
>NUMADAPTERS=3
>
>>while [[ `find /dev/dvb -name 'adapter*' | wc -l` -lt $NUMADAPTERS
>> ]]; do sleep 1; done
>>runvdr ...
>>
>> could be used to count the number of adapters, and check that number in
>> a loop
>> against the expec
On Tue, 20 Aug 2013 10:12:25 +0200
Klaus Schmidinger wrote:
> I wouldn't like to add a dependency to libudev.
Why not?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 20.08.2013 10:42, Klaus Schmidinger wrote:
> On 20.08.2013 10:20, Manuel Reimer wrote:
> >On 08/20/2013 10:12 AM, Klaus Schmidinger wrote:
> >>>So my question to Klaus: Is there something like this planned or would
> >>>a patch be accepted which adds a feature like this? As far as I know a
> >>>
On 20.08.2013 10:20, Manuel Reimer wrote:
On 08/20/2013 10:12 AM, Klaus Schmidinger wrote:
So my question to Klaus: Is there something like this planned or would
a patch be accepted which adds a feature like this? As far as I know a
new dependency (libudev) would be needed.
I wouldn't like to
On 08/20/2013 10:12 AM, Klaus Schmidinger wrote:
So my question to Klaus: Is there something like this planned or would
a patch be accepted which adds a feature like this? As far as I know a
new dependency (libudev) would be needed.
I wouldn't like to add a dependency to libudev.
So how could
On 19.08.2013 23:19, Manuel Reimer wrote:
Hello,
with event based init systems (in my case systemd) it seems to become a big
issue to startup VDR.
If you install VDR on a SSD device, then startup gets *really* fast. Sometimes
that fast, that VDR starts before all devices are initialized.
I'v
On 08/20/2013 09:40 AM, André Weidemann wrote:
Add a line like this after loading the required modules:
/sbin/modprobe dvb
/sbin/udevadm settle --timeout=30
then start up vdr.
Everything should be fine since udevadm only returns after all actions
regarding the module load are settled.
This is
On 19.08.2013 23:19, Manuel Reimer wrote:
Hello,
with event based init systems (in my case systemd) it seems to become a
big issue to startup VDR.
If you install VDR on a SSD device, then startup gets *really* fast.
Sometimes that fast, that VDR starts before all devices are initialized.
Ther
Manuel Reimer writes:
> Hello,
>
> with event based init systems (in my case systemd) it seems to become
> a big issue to startup VDR.
>
> If you install VDR on a SSD device, then startup gets *really*
> fast. Sometimes that fast, that VDR starts before all devices are
> initialized.
>
> I've ask
Hello,
with event based init systems (in my case systemd) it seems to become a
big issue to startup VDR.
If you install VDR on a SSD device, then startup gets *really* fast.
Sometimes that fast, that VDR starts before all devices are initialized.
I've asked in the systemd mailinglist, if th
15 matches
Mail list logo
