2014-08-22, 22:27
Hi Forum,
hopefully this is the right place for my question.
I'm trying to get a basic understanding of the feature "wake remote server on request". I do know the basic meaning of this - xbmc/kodi will broadcast some sort of wakeonlan to the remote server, and that will therefore boot.
But which kind of action will trigger that remote wakeup-call?
Is it when I try to open a media file on said server?
Or when I start watching a channel in LiveTV?
Or will it wake my server whenever xbmc/kodi RUNS?
Background to my question: I'm having a devoted server running easyvdr 2.0, acting as main location for all media files. This server is not always running! It wakes for timers and the like, of course, but goes to poweroff mode after that.
xbmc itself is running on a raspberry pi, and this one is up 24/7 cause it is also acting as a proxy server at the local net. It has the vnsi-pvr-client activated and running fine.
So if the xbmc only wakes the server when I'm either accessing a file on the vdr-smb-share or a channel in LiveTV, all is good.
If it is periodically trying to wake my server just because the vnsi-client is running, it is NOT good. (Then I'd have to look for a widget to manually wake-on-lan the vdr).
Thanks in advance.
hopefully this is the right place for my question.
I'm trying to get a basic understanding of the feature "wake remote server on request". I do know the basic meaning of this - xbmc/kodi will broadcast some sort of wakeonlan to the remote server, and that will therefore boot.
But which kind of action will trigger that remote wakeup-call?
Is it when I try to open a media file on said server?
Or when I start watching a channel in LiveTV?
Or will it wake my server whenever xbmc/kodi RUNS?
Background to my question: I'm having a devoted server running easyvdr 2.0, acting as main location for all media files. This server is not always running! It wakes for timers and the like, of course, but goes to poweroff mode after that.
xbmc itself is running on a raspberry pi, and this one is up 24/7 cause it is also acting as a proxy server at the local net. It has the vnsi-pvr-client activated and running fine.
So if the xbmc only wakes the server when I'm either accessing a file on the vdr-smb-share or a channel in LiveTV, all is good.
If it is periodically trying to wake my server just because the vnsi-client is running, it is NOT good. (Then I'd have to look for a widget to manually wake-on-lan the vdr).
Thanks in advance.