vdr-plugin-upnp verschwunden?

methodus · 24. November 2012

Danke an Keine_Ahnung für den Tipp mit dem Selbstladen. Ich habe die notwendigen Änderungen eingecheckt.

avjui · 24. November 2012

Danke für die Änderungen jetzt lässt sich das Plugin bauen.

Meine Anpassungen im Debian Ordner wären folgende

rules

Code

#!/usr/bin/make -f


# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1


MAKE_OPTIONS = VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale


%:
	dh $@


override_dh_auto_build:
	dh_auto_build -- all $(MAKE_OPTIONS)
	dh_auto_build -- subplugins $(MAKE_OPTIONS)


override_dh_auto_clean:
	$(MAKE) -o .dependencies clean $(MAKE_OPTIONS)
	#clean all libarys
	rm -rf locale libvdr-*.so.*
	rm -rf plugins/profiler/vdrDVBProfiler/libupnp-dvb-profiler*
	rm -rf plugins/profiler/vdrDVBProfiler/dvbProfiler.o
	rm -rf plugins/provider/recProvider/libupnp-rec-provicer*
	rm -rf plugins/provider/recProvider/recProvider.o
	rm -rf plugins/provider/vdrProvider/libupnp-vdr-provider*
	rm -rf plugins/provider/vdrProvider/vdrProvider.o


override_dh_gencontrol:
	sh /usr/share/vdr-dev/dependencies.sh
	dh_gencontrol


override_dh_auto_install:


override_dh_strip:
	dh_strip --dbg-package=vdr-plugin-upnp-dbg

Alles anzeigen

und die install

Code

libvdr-upnp.so.*    								usr/lib/vdr/plugins/
plugins/profiler/vdrDVBProfiler/libupnp-*-profiler.so.*			usr/lib/vdr/plugins/
plugins/provider/recProvider/libupnp-*-provider.so.*		 	usr/lib/vdr/plugins/
plugins/provider/vdrProvider/libupnp-*-provider.so.*			usr/lib/vdr/plugins/
locale             								usr/share/

mfg

ollo · 27. November 2012

Moin,

Ich habe das Plugin aus dem unstable-vdr repo installiert und seit dem schreibt der VDR ständig auf die Systemplatte, was den jbd2/sdb1-8 Prozess des ext4 triggert.

Code

Nov 27 21:09:21 hdtv kernel: [ 1102.326417] vdr(4137): dirtied inode 131858 (metadata.db-journal) on sdb1
Nov 27 21:09:21 hdtv kernel: [ 1102.326430] vdr(4137): dirtied inode 131858 (metadata.db-journal) on sdb1
Nov 27 21:09:21 hdtv kernel: [ 1102.327151] vdr(4137): WRITE block 5307640 on sdb1 (16 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328366] jbd2/sdb1-8(286): WRITE block 4689200 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328539] jbd2/sdb1-8(286): WRITE block 4689208 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328551] jbd2/sdb1-8(286): WRITE block 4689216 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328558] jbd2/sdb1-8(286): WRITE block 4689224 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328565] jbd2/sdb1-8(286): WRITE block 4689232 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328573] jbd2/sdb1-8(286): WRITE block 4689240 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328580] jbd2/sdb1-8(286): WRITE block 4689248 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328587] jbd2/sdb1-8(286): WRITE block 4689256 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328594] jbd2/sdb1-8(286): WRITE block 4689264 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.328602] jbd2/sdb1-8(286): WRITE block 4689272 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.330938] jbd2/sdb1-8(286): WRITE block 4689280 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.331815] jbd2/sdb1-8(286): WRITE block 4689288 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.331844] jbd2/sdb1-8(286): WRITE block 4689296 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.331854] jbd2/sdb1-8(286): WRITE block 4689304 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.332855] jbd2/sdb1-8(286): WRITE block 4689312 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.334090] vdr(4137): WRITE block 5307640 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.335328] jbd2/sdb1-8(286): WRITE block 4689320 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.335366] jbd2/sdb1-8(286): WRITE block 4689328 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.335379] jbd2/sdb1-8(286): WRITE block 4689336 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.335386] jbd2/sdb1-8(286): WRITE block 4689344 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.336866] jbd2/sdb1-8(286): WRITE block 4689352 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.337790] vdr(4137): WRITE block 795448 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.337840] vdr(4137): WRITE block 10202984 on sdb1 (16 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.337862] vdr(4137): WRITE block 10203168 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.337881] vdr(4137): WRITE block 10203280 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.411354] jbd2/sdb1-8(286): WRITE block 4689360 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.411385] jbd2/sdb1-8(286): WRITE block 4689368 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.411395] jbd2/sdb1-8(286): WRITE block 4689376 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.411402] jbd2/sdb1-8(286): WRITE block 4689384 on sdb1 (8 sectors)
Nov 27 21:09:21 hdtv kernel: [ 1102.412878] jbd2/sdb1-8(286): WRITE block 4689392 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.427000] vdr(4137): dirtied inode 131858 (metadata.db-journal) on sdb1
Nov 27 21:09:22 hdtv kernel: [ 1102.427013] vdr(4137): dirtied inode 131858 (metadata.db-journal) on sdb1
Nov 27 21:09:22 hdtv kernel: [ 1102.427738] vdr(4137): WRITE block 5307656 on sdb1 (16 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.428954] jbd2/sdb1-8(286): WRITE block 4689400 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.428980] jbd2/sdb1-8(286): WRITE block 4689408 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.428989] jbd2/sdb1-8(286): WRITE block 4689416 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.428996] jbd2/sdb1-8(286): WRITE block 4689424 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.429004] jbd2/sdb1-8(286): WRITE block 4689432 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.429011] jbd2/sdb1-8(286): WRITE block 4689440 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.429018] jbd2/sdb1-8(286): WRITE block 4689448 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.429025] jbd2/sdb1-8(286): WRITE block 4689456 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.429032] jbd2/sdb1-8(286): WRITE block 4689464 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.429039] jbd2/sdb1-8(286): WRITE block 4689472 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.431378] jbd2/sdb1-8(286): WRITE block 4689480 on sdb1 (8 sectors)
Nov 27 21:09:22 hdtv kernel: [ 1102.432203] jbd2/sdb1-8(286): WRITE block 4689488 on sdb1 (8 sectors)

Alles anzeigen

Was passiert da? Meiner SDD bekommt das sicher nicht

Gruß, ollo

methodus · 27. November 2012

Das ist die Metadata.db, die dort geschrieben wird. Es wäre anzuraten, bei Systemen, die spezielle Absicherungen von Schreibvorgängen haben, die Datenbank in ein RAM-FS zu legen und beim Runterfahren persistent zu speichern.

Ich hab auf meiner Liste, die Schreibvorgänge zunächst im RAM zu machen und beim Shutdown zu schreiben, aber da hab ich noch nicht angefangen.

vdr-plugin-upnp verschwunden?

Jetzt mitmachen!

Teilen