Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: Problem with vdr and hdd full
On Samstag, 12. April 2003 17:20 Matthias Fechner wrote:
> Yes, i can reproduce it.
> I had the following diskconfiguration:
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda3 2.0G 1.6G 441M 78% /
> /dev/hda1 19M 6.5M 13M 35% /boot
> /dev/hda4 151G 151G 55M 100% /video0
> /dev/hdb1 77G 77G 68M 100% /video1
> /dev/hdc1 75G 75G 73M 100% /video2
> /dev/hdd1 75G 74G 642M 100% /video3
> server:/usr/home/mp3 19G 19G 80M 100% /home/mp3
> server:/usr/home/storage
> 42G 37G 1.6G 97% /home/storage
>
> Than i start i timer.
> I have attached the part of the logfile.
>
> > Do you get a core dump with which you could do a stack trace to
> > find out where exactly it crashes?
>
> I cannot found any vdr.core. Should vdr or linux create this file in
> the vdr-dir(vdr is directly started from /usr/local/video/VDR)?
The corefile is produced in the working directory (the dir VDR is started
from). It is called "core" or "core.<pid>" depending on your configuration.
It contains a dump of the memory when the program crashed.
You have to check ulimit's first. Type ulimit -a on the commandline. If you
see the following line:
core file size (blocks) 0
you must ENABLE core file creation first using "ulimit -c unlimited".
Otherwise corefiles are not created so the harddisk is not polluted.
After enabling corefiles, just start vdr and wait til it crashes...
Greetings,
Sascha Volkenandt
--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.
Home |
Main Index |
Thread Index