legenwaitforitdary
Meister
- Registriert
- 12. November 2011
- Beiträge
- 757
- Reaktionspunkte
- 147
- Punkte
- 103
Öhm, ist denn in Wheezy nicht noch vdr 1.7.irgendwas enthalten?
Ansonsten ist ja schön, dass es doch mal jemand zum Laufen gebracht hat. ;-)
Kannst du bitte noch die Ausgabe von apt-cache policy vdr posten?
Wenn dein ursprüngliches Ziel war vdr 2.1.6 auf der Kiste laufen zu lassen, war die ganze bisherige Aktion eigentlich fürn A...
Ich glaub nicht dass es da was fertiges gibt, aber wird sicher auch funktionieren.
vdr:
Installiert: 2.0.3-1~etobi1
Installationskandidat: 2.0.3-1~etobi1
Versionstabelle:
*** 2.0.3-1~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
100 /var/lib/dpkg/status
2.0.1-1~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
2.0.0-1~etobi4 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
2.0.0-1~etobi3 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
2.0.0-1~etobi2 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
2.0.0-1~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
1.7.42-2~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
1.7.42-1~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
1.7.41-1~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
1.7.40-1~etobi1 0
995 http://e-tobi.net/vdr-experimental/ wheezy/vdr-multipatch amd64 Pack ages
1.7.28-1 0
990 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages
Oscam mit Simplebuild kompiliert?
Kannst du mal dein vorgehen posten,wären dir einige dankbar.
Unter Ubuntu Server läuft zwar alles,nur es ist ein wenig träge.
Endpacken oder auch das verschieben im Netztwerk,ist um einiges langsamer als OMV
apt-get install libcxxtools-dev libtntnet-dev libboost-dev pkg-config subversion unzip build-essential libjpeg62-dev libcap-dev libfontconfig1-dev gettext libncursesw5-dev libncurses5-dev git libdvbcsa-dev git vdr-dev
svn co svn://svn.speedbox.me/svn/oscam-install/trunk oscam
chmod -R 0755 oscam
cd oscam
./install
#! /bin/sh
###### #### ##### ##### ### ###
## ## ## ## ## ## ## ## ##
## ## ##### ## ####### ## ## ##
## ## ## ## ## ## ## ##
###### #### ##### ## ## ## ## R
################################################################
# Title:.......restart.sh #
# Author:......Prilly #
# Support:.....prilly@speedbox.me #
# Date:........18 June 2013 #
# Description:.Automaticaly install OScam and support scripts #
# Updates OScam to latest or specific version #
################################################################
### BEGIN INIT INFO
# Provides: OScam
# Required-Start: $local_fs $remote_fs $syslog $network
# Required-Stop:
# Should-Start:
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: start and stop the OScam server
# Description: OScam is a cardserver
### END INIT INFO
if ! ps x |grep -v grep |grep -c /usr/bin/oscam >/dev/null
then
if -f /etc/init.d/oscam
then
/etc/init.d/oscam start
echo `date "+%d/%m/%y %R process was not working"` >> /var/log/oscam/oscam_restart_log
else
echo `date "+%d/%m/%y %R /etc/init.d/oscam is missing"` >> /var/log/oscam/oscam_restart_log
fi
# This part above will check if there is NO oscam process running.
# And if this condition it truth, it will start it and write to log.
# Log entry will contain time stamp and reason of execution (process not working)
# If first condition in not truth (oscam was running), go further to next condition.
elif
tail -8 /var/log/oscam/oscam.log |grep -v grep |grep -c ins40 >/dev/null
then
/etc/init.d/oscam restart
echo `date "+%d/%m/%y %R ins40 error detected"` >> /var/log/oscam/oscam_restart_log
elif
tail -8 /var/log/oscam/oscam.log |grep -v grep |grep -c trylock >/dev/null
then
/etc/init.d/oscam restart
echo `date "+%d/%m/%y %R trylock error detected"` >> /var/log/oscam/oscam_restart_log
# Those 2 conditions will look for 2 common errors in Oscam: "ins40" and "trylock"
# If last 8 lines of your oscam.log contain any of those errors, it will restart oscam.
# Log entries will include the exact reason of restart.
# ins40 error is random error that will keep oscam running but no CWs returned.
# trylock is older error that appear if you use CCcam protocol in oscam.server
# If oscam passes all conditions and all is OK, it will simply echo "ok" :-)
else
echo "ok"
fi
# ENJOY - Prilly
[dvbapi]
enabled = 1
au = 1
boxtype = pc
user = vdr
pmt_mode = 4
[B]/etc/init.d/oscam start[/B]
[LIST=1]
[*]/etc/init.d/vdr stop
[*]cd /
[*]wget https://launchpad.net/ubuntu/+archive/primary/+files/vdr_2.0.3.orig.tar.bz2
[*]tar -xvf vdr_2.0.3.orig.tar.bz2
[*]mv vdr-2.0.3 vdr
[*]cd vdr/Plugins/src
[*]git clone git://github.com/manio/vdr-plugin-dvbapi.git dvbapi
[*]cd dvbapi
[*]git checkout v1.0.6
[*]make
[*]make install
[/LIST]
apt-get install vdr-plugin-xvdr
[COLOR=#333333]apt-get install libcxxtools-dev libtntnet-dev libboost-dev pkg-config subversion unzip build-essential libjpeg62-dev libcap-dev libfontconfig1-dev gettext libncursesw5-dev libncurses5-dev git libdvbcsa-dev vdr-dev make[/COLOR]
cd /
wgetSie müssen registriert sein, um Links zu sehen.
tar -xvf vdr_2.0.3.orig.tar.bz2
mv vdr-2.0.3 vdr
cd vdr/Plugins/src
git clone git://github.com/manio/vdr-plugin-dvbapi.git dvbapi
cd dvbapi
git checkout v1.0.6
make
make install
[COLOR=#333333]-B0[/COLOR]
[COLOR=#333333]svn co svn://svn.speedbox.me/svn/oscam-install/trunk oscam
[/COLOR]chmod -R 0755 oscam
cd oscam
./install
#! /bin/sh
###### #### ##### ##### ### ###
## ## ## ## ## ## ## ## ##
## ## ##### ## ####### ## ## ##
## ## ## ## ## ## ## ##
###### #### ##### ## ## ## ## R
################################################################
# Title:.......restart.sh #
# Author:......Prilly #
# Support:.....prilly@speedbox.me #
# Date:........18 June 2013 #
# Description:.Automaticaly install OScam and support scripts #
# Updates OScam to latest or specific version #
################################################################
### BEGIN INIT INFO
# Provides: OScam
# Required-Start: $local_fs $remote_fs $syslog $network
# Required-Stop:
# Should-Start:
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: start and stop the OScam server
# Description: OScam is a cardserver
### END INIT INFO
if ! ps x |grep -v grep |grep -c /usr/bin/oscam >/dev/null
then
if -f /etc/init.d/oscam
then
/etc/init.d/oscam start
echo `date "+%d/%m/%y %R process was not working"` >> /var/log/oscam/oscam_restart_log
else
echo `date "+%d/%m/%y %R /etc/init.d/oscam is missing"` >> /var/log/oscam/oscam_restart_log
fi
# This part above will check if there is NO oscam process running.
# And if this condition it truth, it will start it and write to log.
# Log entry will contain time stamp and reason of execution (process not working)
# If first condition in not truth (oscam was running), go further to next condition.
elif
tail -8 /var/log/oscam/oscam.log |grep -v grep |grep -c ins40 >/dev/null
then
/etc/init.d/oscam restart
echo `date "+%d/%m/%y %R ins40 error detected"` >> /var/log/oscam/oscam_restart_log
elif
tail -8 /var/log/oscam/oscam.log |grep -v grep |grep -c trylock >/dev/null
then
/etc/init.d/oscam restart
echo `date "+%d/%m/%y %R trylock error detected"` >> /var/log/oscam/oscam_restart_log
# Those 2 conditions will look for 2 common errors in Oscam: "ins40" and "trylock"
# If last 8 lines of your oscam.log contain any of those errors, it will restart oscam.
# Log entries will include the exact reason of restart.
# ins40 error is random error that will keep oscam running but no CWs returned.
# trylock is older error that appear if you use CCcam protocol in oscam.server
# If oscam passes all conditions and all is OK, it will simply echo "ok" :-)
else
echo "ok"
fi
# ENJOY - Prilly
[B]/etc/init.d/vdr restart
[/B][B]/etc/init.d/oscam restart[/B]
# /etc/default/vdr
#
# See also /usr/share/doc/vdr/README.Debian.gz
#
[COLOR=#ff0000]VDR_CHARSET_OVERRIDE=ISO-8859-9[/COLOR]
# Change to 1 to enable vdr's init-script
ENABLED=1
# Change this to 1 if you want vdr to be able to shutdown the
# computer
ENABLE_SHUTDOWN=0
# Options that will be passed to vdr's commandline
OPTIONS="-w 60 --filesize 5G -l 1"
OPTIONS="-w 60 --filesize 5G -l 1"
VIDEO_DIR="Dein Aufnahme Verzeichnis hier rein"
Wir verwenden Cookies und ähnliche Technologien für folgende Zwecke:
Akzeptieren Sie Cookies und diese Technologien?
Wir verwenden Cookies und ähnliche Technologien für folgende Zwecke:
Akzeptieren Sie Cookies und diese Technologien?