linux:vdr_konflikt_mail
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| blog:linux:vdr_konflikt_mail [30.09.2010 16:33] – eanderalx | blog:linux:vdr_konflikt_mail [06.10.2010 22:22] – eanderalx | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| **Problems: | **Problems: | ||
| * I'm using my vdr without a client and without OSD. | * I'm using my vdr without a client and without OSD. | ||
| - | * I don't find a nice possibility to send a mail when a conflict occurs | + | * I doesn't find a pleasant |
| - | * A exististing | + | * By using epgsearch, a conflict |
| + | * A existing | ||
| ===== Prerequisite ===== | ===== Prerequisite ===== | ||
| - | * All logs produced by vdr produziert | + | * All logs produced by vdr are collected by syslog-ng into a single file so that can be analysed. |
| **Syslog-ng.conf (part of it): | **Syslog-ng.conf (part of it): | ||
| < | < | ||
| Line 36: | Line 37: | ||
| </ | </ | ||
| </ | </ | ||
| + | |||
| + | ===== Monitoring the log ===== | ||
| + | |||
| + | |||
| * Every 30min, or something like that, vdr checks for timer-conflicts (It's a German System) | * Every 30min, or something like that, vdr checks for timer-conflicts (It's a German System) | ||
| < | < | ||
| Line 43: | Line 48: | ||
| </ | </ | ||
| **Analysing the log isn't complicated: | **Analysing the log isn't complicated: | ||
| - | * mailx only works without additional options when [[blog: | + | * mailx only works without additional options when [[blog: |
| <file bash vdr_timer_konflikte.sh> | <file bash vdr_timer_konflikte.sh> | ||
linux/vdr_konflikt_mail.txt · Last modified: 23.03.2013 18:44 by eanderalx
