yaVDR 0.5: Lifeguard und Avahi-Mounter

JurKub · 9. Januar 2013

Hi all,

mir ist aufgefallen, dass wenn ich die NFS Freigaben vom VDR-Server über Avahi-Mounter auf dem VDR-Client einbinde der VDR-Server recht häufig dennoch runter fährt.

Mount ich die NFS Freigaben via Script /etc/network/if-up.d/vdr-nfs funktioniert es zuverlässig.

Any idea ?

Thx
JurKub

seahawk1986 · 9. Januar 2013

Zitat von JurKub

Any idea ?

Syslogs und Shutdown-Hooks ansehen und testen unter welcher Konstellation das genau passiert.

JurKub · 10. Januar 2013

Ausgelöst durch Anwählen von System -> Befehle -> System herunterfahren auf VDR-Server

Bei ersten Mal wurde der Shutdown abgebrochen -> NFS Mount und beim zweiten Mal ist der VDR-Server runtergefahren (siehe Syslogs).

Die Shutdown-Hooks auf VDR-Server und Client sind Standard

Syslog vom VDR-Server:

Code

Jan 10 08:15:00 VDR-Office vdr: [930] executing command '/usr/bin/vdr-dbus-send /Remote remote.HitKey string:'Power' &> /dev/null & '
Jan 10 08:15:00 VDR-Office vdr: [1023] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member HitKey
Jan 10 08:15:00 VDR-Office vdr: [1023] dbus2vdr: 1 idle message handler, reusing 0x7f8db400e750
Jan 10 08:15:00 VDR-Office vdr: [2297] dbus2vdr message handler thread started (pid=930, tid=2297)
Jan 10 08:15:00 VDR-Office vdr: [2297] dbus2vdr: de.tvdr.vdr.remote.HitKey: get key 'Power'
Jan 10 08:15:00 VDR-Office vdr: [930] Power button pressed
Jan 10 08:15:00 VDR-Office vdr: [930] confirm: Taste drücken, um Ausschalten abzubrechen
Jan 10 08:15:00 VDR-Office vdr: [930] warning: Taste drücken, um Ausschalten abzubrechen
Jan 10 08:15:00 VDR-Office vdr: [930] [xine..put] cXinelibOsd::CanHandleAreas(): Device does not support ARGB
Jan 10 08:15:00 VDR-Office vdr: [2297] dbus2vdr: moving message handler 0x7f8db400e750 from active to finished
Jan 10 08:15:00 VDR-Office vdr: [2297] dbus2vdr message handler thread ended (pid=930, tid=2297)
Jan 10 08:15:00 VDR-Office vdr: [1023] dbus2vdr: connection has messages to send, flushing
Jan 10 08:15:00 VDR-Office vdr: [1023] dbus2vdr: done flushing
Jan 10 08:15:06 VDR-Office vdr: [930] confirmed
Jan 10 08:15:06 VDR-Office vdr: [930] next timer event at Thu Jan 10 16:03:00 2013
Jan 10 08:15:06 VDR-Office vdr: [930] executing '/usr/lib/vdr/vdr-shutdown.wrapper 1357830180 28074 45 "Juergen-HD~X:enius~Autoimmunkrankheiten - Wenn die körperei" 1'
Jan 10 08:15:06 VDR-Office vdr: [930] saved setup to /var/lib/vdr/setup.conf
Jan 10 08:15:06 VDR-Office vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.acpiwakeup as shell script
Jan 10 08:15:06 VDR-Office vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2013-01-10 14:58:00
Jan 10 08:15:06 VDR-Office vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Jan 10 08:15:06 VDR-Office vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Jan 10 08:15:06 VDR-Office vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom
Jan 10 08:15:06 VDR-Office vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Jan 10 08:15:06 VDR-Office vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Jan 10 08:15:06 VDR-Office vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Jan 10 08:15:06 VDR-Office vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S99.shutdown
Jan 10 08:15:06 VDR-Office kernel: [ 5250.506570] init: graphtft-fe main process (1179) killed by TERM signal
Jan 10 08:15:07 VDR-Office kernel: [ 5250.583102] init: graphtft-fe post-stop process (2364) terminated with status 2
Jan 10 08:15:07 VDR-Office vdr: [1148] [xine..put] Closing connection 0
Jan 10 08:15:07 VDR-Office kernel: [ 5250.752831] init: vdr-frontend main process (1016) terminated with status 1
Jan 10 08:15:07 VDR-Office vdr: [930] stopping plugin: xvdr
Jan 10 08:15:07 VDR-Office vdr: [930] XVDR: XVDR Server stopped
Jan 10 08:15:07 VDR-Office vdr: [930] stopping plugin: xineliboutput
Jan 10 08:15:07 VDR-Office vdr: [930] [xine..put] cXinelibDevice::StopDevice(): Stopping device ...
Jan 10 08:15:07 VDR-Office vdr: [1153] TS buffer on device 1 thread ended (pid=930, tid=1153)
Jan 10 08:15:07 VDR-Office vdr: [1152] buffer stats: 5452 (0%) used
Jan 10 08:15:07 VDR-Office vdr: [1152] receiver on device 1 thread ended (pid=930, tid=1152)
Jan 10 08:15:08 VDR-Office vdr: [1148] Remote decoder/display server (cXinelibServer) thread ended (pid=930, tid=1148)
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: text2skin
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: svdrpservice
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: streamdev-server
Jan 10 08:15:08 VDR-Office vdr: [1035] streamdev server thread ended (pid=930, tid=1035)
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: skinpearlhd
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: restfulapi
Jan 10 08:15:08 VDR-Office vdr: [930] restfulapi: will end server thread: /1357802108/
Jan 10 08:15:08 VDR-Office vdr: [1034] restfulapi: server thread end: /1357802108/
Jan 10 08:15:08 VDR-Office vdr: [1034] restfulapi: server thread ended (pid=930)
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: quickepgsearch
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: menuorg
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: live
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: graphtft
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: fritzbox
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/Listener.cpp:64] deleting listener
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/FonbookManager.cpp:119] deleting Fonbook Manager
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/FonbookManager.cpp:75] deleting fonbook with ID: FRITZ
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/FonbookManager.cpp:75] deleting fonbook with ID: OERT
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/FonbookManager.cpp:75] deleting fonbook with ID: LOCCH
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/FonbookManager.cpp:75] deleting fonbook with ID: ZOEK
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/FonbookManager.cpp:75] deleting fonbook with ID: LOCL
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/CallList.cpp:110] deleting call list
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/CallList.cpp:119] deleted call list
Jan 10 08:15:08 VDR-Office vdr: [930] [libfritz++/Config.cpp:82] Shutdown of libfritz++ completed.
Jan 10 08:15:08 VDR-Office vdr: [930] stopping plugin: extrecmenu
Jan 10 08:15:09 VDR-Office vdr: [1026] extrecmenu worker thread thread ended (pid=930, tid=1026)
Jan 10 08:15:09 VDR-Office vdr: [930] stopping plugin: epgsearchonly
Jan 10 08:15:09 VDR-Office vdr: [930] stopping plugin: epgsearch
Jan 10 08:15:09 VDR-Office vdr: [1024] EPGSearch: Leaving search timer thread
Jan 10 08:15:09 VDR-Office vdr: [1024] EPGSearch: searchtimer thread ended (pid=930, tid=1024)
Jan 10 08:15:09 VDR-Office vdr: [930] stopping plugin: dbus2vdr
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: emit upstart-signal stopped for all plugins
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: upstart-signal stopped queued
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: stop DBus-Upstart-Signal-Sender
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: dequeue signal vdr-plugin/stopped
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: retrieving connection for sending signal
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: SendSignal Lock
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: SendSignal Unlock
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: SendSignal: dbus_connection_send
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: SendSignal: dbus_message_unref
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: signal sent
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: emit upstart-signal vdr-plugin for stopped
Jan 10 08:15:09 VDR-Office vdr: [1178] dbus2vdr: DBus-Upstart-Signal-Sender thread ended (pid=930, tid=1178)
Jan 10 08:15:09 VDR-Office vdr: [1023] dbus2vdr: connection has messages to send, flushing
Jan 10 08:15:09 VDR-Office vdr: [1023] dbus2vdr: done flushing
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: delete DBus-Upstart-Signal-Sender
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: StopMonitor Lock
Jan 10 08:15:09 VDR-Office vdr: [1023] dbus2vdr: monitor stopped on bus de.tvdr.vdr
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: StopMonitor Unlock 2
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting 1 message handlers
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.epg
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.osd
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.plugin
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.recording
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.remote
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.setup
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.shutdown
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.skin
Jan 10 08:15:09 VDR-Office vdr: [930] dbus2vdr: deleting message dispatcher for interface de.tvdr.vdr.timer
Jan 10 08:15:09 VDR-Office vdr: [930] stopping plugin: control
Jan 10 08:15:09 VDR-Office vdr: [930] stopping plugin: conflictcheckonly
Jan 10 08:15:09 VDR-Office vdr: [930] [xine..put] cXinelibOsdProvider: shutting down !
Jan 10 08:15:09 VDR-Office vdr: [930] GraphTFT plugin try to stop communication thread
Jan 10 08:15:09 VDR-Office vdr: [1031] GraphTFT plugin tcp communication thread ended (pid=930)
Jan 10 08:15:09 VDR-Office vdr: [1967] KBD remote control thread ended (pid=930, tid=1967)
Jan 10 08:15:10 VDR-Office vdr: [930] saved setup to /var/lib/vdr/setup.conf
Jan 10 08:15:10 VDR-Office vdr: [1006] section handler thread ended (pid=930, tid=1006)
Jan 10 08:15:10 VDR-Office vdr: [1005] tuner on frontend 0/0 thread ended (pid=930, tid=1005)
Jan 10 08:15:10 VDR-Office vdr: [1009] section handler thread ended (pid=930, tid=1009)
Jan 10 08:15:10 VDR-Office vdr: [1008] tuner on frontend 1/0 thread ended (pid=930, tid=1008)
Jan 10 08:15:10 VDR-Office vdr: [1012] section handler thread ended (pid=930, tid=1012)
Jan 10 08:15:10 VDR-Office vdr: [1011] tuner on frontend 2/0 thread ended (pid=930, tid=1011)
Jan 10 08:15:10 VDR-Office vdr: [1015] section handler thread ended (pid=930, tid=1015)
Jan 10 08:15:10 VDR-Office vdr: [1014] tuner on frontend 3/0 thread ended (pid=930, tid=1014)
Jan 10 08:15:10 VDR-Office vdr: [930] [xine..put] cXinelibDevice::StopDevice(): Stopping device ...
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: xvdr
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: xineliboutput
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: text2skin
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: svdrpservice
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: streamdev-server
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: skinpearlhd
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: restfulapi
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: quickepgsearch
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: menuorg
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: live
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: graphtft
Jan 10 08:15:10 VDR-Office vdr: [1032] GraphTFT plugin display thread ended (pid=930)
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: fritzbox
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: extrecmenu
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: epgsearchonly
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: epgsearch
Jan 10 08:15:10 VDR-Office vdr: [1025] EPGSearch: Leaving conflict check thread
Jan 10 08:15:10 VDR-Office vdr: [1025] EPGSearch: conflictcheck thread ended (pid=930, tid=1025)
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: dbus2vdr
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: control
Jan 10 08:15:10 VDR-Office vdr: [1022] [control] gateways thread ended (pid=930)
Jan 10 08:15:10 VDR-Office vdr: [930] deleting plugin: conflictcheckonly
Jan 10 08:15:10 VDR-Office kernel: [ 5254.207030] vdr[2293]: segfault at 7f8df729b781 ip 00007f8df729b781 sp 00007f8da5ffada0 error 14 in ISO8859-9.so[7f8df76a7000+2000]
Jan 10 08:15:10 VDR-Office kernel: [ 5254.320397] init: vdr main process (930) killed by SEGV signal
Jan 10 08:15:10 VDR-Office acpid: exiting
Jan 10 08:15:10 VDR-Office lircd-0.9.0[872]: removed client
Jan 10 08:15:10 VDR-Office kernel: [ 5254.449713] init: smbd main process (852) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.449977] init: irexec main process (867) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.450298] init: idmapd main process (863) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.453236] init: udisks-automounter main process (1156) terminated with status 143
Jan 10 08:15:10 VDR-Office kernel: [ 5254.455576] init: tty4 main process (1462) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.456143] init: tty5 main process (1464) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.456835] init: lircd2uinput main process (874) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.457366] init: tty2 main process (1471) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.457904] init: tty3 main process (1472) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.458644] init: tty6 main process (1475) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.459671] init: cron main process (1505) killed by TERM signal
Jan 10 08:15:10 VDR-Office lircd-0.9.0[872]: caught signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.461396] init: tty1 main process (1681) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.462883] init: plymouth-upstart-bridge main process (2374) terminated with status 1
Jan 10 08:15:10 VDR-Office kernel: [ 5254.469504] init: lircd main process (872) killed by TERM signal
Jan 10 08:15:10 VDR-Office kernel: [ 5254.496497] init: eventlircd main process (834) killed by TERM signal
Jan 10 08:15:11 VDR-Office kernel: [ 5254.780491] HDMI hot plug event: Codec=2 Pin=5 Presence_Detect=1 ELD_Valid=0
Jan 10 08:15:11 VDR-Office kernel: [ 5254.788006] HDMI status: Codec=2 Pin=5 Presence_Detect=0 ELD_Valid=0
Jan 10 08:15:11 VDR-Office rpc.mountd[1648]: Caught signal 15, un-registering and exiting.
Jan 10 08:15:11 VDR-Office avahi-daemon[1643]: Got SIGTERM, quitting.
Jan 10 08:15:11 VDR-Office avahi-daemon[1643]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::21b:fcff:fe84:9ec.
Jan 10 08:15:11 VDR-Office avahi-daemon[1643]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.0.50.
Jan 10 08:15:11 VDR-Office avahi-daemon[1643]: avahi-daemon 0.6.30 exiting.
Jan 10 08:15:11 VDR-Office kernel: [ 5255.346110] init: openbox main process (901) terminated with status 1
Jan 10 08:15:16 VDR-Office kernel: [ 5260.053395] nfsd: last server has exited, flushing export cache
Jan 10 08:15:17 VDR-Office rpc.statd[890]: Caught signal 15, un-registering and exiting
Jan 10 08:15:17 VDR-Office rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Jan 10 08:15:17 VDR-Office kernel: [ 5260.836758] init: statd main process (890) terminated with status 1
Jan 10 08:15:17 VDR-Office kernel: [ 5260.837544] init: portmap main process (708) terminated with status 2
Jan 10 08:15:17 VDR-Office kernel: [ 5260.850938] init: Disconnected from system bus
Jan 10 08:15:17 VDR-Office dhclient: DHCPRELEASE on eth0 to 10.0.0.1 port 67
Jan 10 08:15:17 VDR-Office kernel: Kernel logging (proc) stopped.

Alles anzeigen

Syslog vom VDR-Client:

Code

Jan 10 08:15:12 VDR-Living avahi-mounter[1637]: umounting /media/Musik/VDR-Office/ on server logout
Jan 10 08:15:12 VDR-Living avahi-mounter[1637]: umounting /media/Bilder/VDR-Office/ on server logout
Jan 10 08:15:12 VDR-Living avahi-mounter[1637]: umounting /srv/vdr/video.00/VDR-Office/ on server logout

JurKub · 11. Januar 2013

Hi all,

kann jemand mit den Infos was anfangen oder ist das zu wenig ?

Thx
JurKub

seahawk1986 · 11. Januar 2013

Es muss ja am lifeguard-Addon hängen - in der /etc/vdr/lifeguard.conf sollte es so einen Eintrag geben:

Code

tcp     nfs             NFS\ Mount\ is\ still\ active

Sinngemäß mach es dann in der /usr/share/vdr/shutdown-hooks/S91.lifeguard damit für NFS so eine Abfrage:

Code

PATTERN=nfs
if [ $(netstat -t | grep -e "^tcp" | grep -ve "CLOSE_WAIT[ \t]*$" | sed -re "s/ +/ /g" | cut -d " " -f 4 | grep -cE ":$PATTERN\b") -gt 0 ]; then
    REASON=${DESCRIPTION:-"$PATTERN"}
fi
# if there is a reason not to shutdown, tell VDR about it
if [ "$REASON" ]; then
        MESSAGE="$REASON"
        # add an explanation to syslog that includes the reason
#       logger -t "$DESC" "$MESSAGE"
        echo "ABORT_MESSAGE=\"$MESSAGE\""
        exit 1
fi

Alles anzeigen

Wenn die Abfrage etwas findet, bricht der VDR den Shutdown ab, ansonsten fährt der VDR dann herunter. Du müsstest also herausfinden, warum die fehlschlägt.

JurKub · 11. Januar 2013

yep, soweit war ich auch schon

Hast du einen Tip wie ich das checken soll ? Wenn ich per ssh auf dem Rechner bin fährt er ja deshalb nicht runter !

Kann man das Ergebnis der If-Abfrage ins syslog schreiben ?

seahawk1986 · 11. Januar 2013

Zitat von JurKub

Wenn ich per ssh auf dem Rechner bin fährt er ja deshalb nicht runter !

Das Verhalten lässt sich ja abschalten (WFE oder direkt in der Konfigurationsdatei).

Zitat von JurKub

Kann man das ergebnis des Tests ins syslog schreiben ?

Klar, für sowas gibt es z.B. das Tool "logger"

JurKub · 11. Januar 2013

OK, werd mal testen

JurKub · 11. Januar 2013

Die NFS Verbindung scheint nach 5 Minuten abzulaufen wenn auf dem VDR-Client keine Aktivität ist, d.h. man nur live (egal ob über lokale Sat-Karte oder via Streamdev-Client) fernsieht.

netstat -t | grep ":nfs\b" bleibt leer

Es reicht schon einmal des Menü auf zumachen dann ist sie auf dem VDR-Server wieder offen

seahawk1986 · 11. Januar 2013

Zitat von JurKub

Die NFS connection scheint "auszutimen" wenn auf dem VDR-Client keine Aktivität ist, d.h. man nur live fernsieht.

Das wäre ja eigentlich die gewünschte Konstellation. Wenn der Server dauherhaft aktiv bleiben soll, solange der Client läuft, bietet sich ja eher die Abfrage nach dem host statt nach einer tcp-Verbindung in der lifeguard.conf des Servers an:

Code

host <IP des Clients> Client\ still\ alive

JurKub · 11. Januar 2013

für Aufnahmen ja, beim Steamdev-Client ist das aber eher unschön

seahawk1986 · 11. Januar 2013

Wenn Streamdev streamt, ist das aber eigentlich Plugin-Aktivität, die das Herunterfahren des Servers verhindern sollte. Wie gesagt wenn der Server auf jeden Fall anbleiben soll, wenn der Client läuft, geht man am besten über eine host-Regel.

JurKub · 11. Januar 2013

OK, hab die beiden Hostnamen der Clients in die lifeguard.conf des Servers eingertragen

Danke für deine Hilfe

Gruß
JurKub

yaVDR 0.5: Lifeguard und Avahi-Mounter

Jetzt mitmachen!

Teilen