Left overs for 'X' and 'V' series - Revision history

Lsuser1985: /* How does the "auto" mode work? */

Lsuser1985 — Fri, 18 Jan 2013 15:25:30 GMT

How does the "auto" mode work?

← Older revision		Revision as of 15:25, 18 January 2013
Line 1:		Line 1:
	== How does the "auto" mode work? ==		== How does the "auto" mode work? ==
-	There is a process running, waiting for WoL packets to arrive.~~<br>~~	+	* There is a process running, waiting for WoL packets to arrive.
-	This process can be found as "pwrmgr" in the process list.~~<br>~~	+	* This process can be found as "pwrmgr" in the process list.
-	In addition to this, there is a script "/usr/local/sbin/pmcd_exec.sh" which uses a feature of the pwrmgr to keep the box alive even if there is no client anymore (e.g. in case of running backups, RAID recovery, running disk format etc.).	+	* In addition to this, there is a script "/usr/local/sbin/pmcd_exec.sh" which uses a feature of the pwrmgr to keep the box alive even if there is no client anymore (e.g. in case of running backups, RAID recovery, running disk format etc.).

	== How to keep a box alive without a client in "auto" mode? ==		== How to keep a box alive without a client in "auto" mode? ==

Lsuser1985: /* Python */ update description, make WoL-script more easy to adopt

Lsuser1985 — Fri, 18 Jan 2013 15:24:37 GMT

Python: update description, make WoL-script more easy to adopt

← Older revision		Revision as of 15:24, 18 January 2013
Line 27:		Line 27:
	Not everyone likes to use the utilities Buffalo provided (if they are available for the intended target operating system at all).<br>		Not everyone likes to use the utilities Buffalo provided (if they are available for the intended target operating system at all).<br>
	=== Python ===		=== Python ===
-	~~Network~~ is a private class B network (10.131.0.0 - 10.131.255.255), netmask is 255.255.0.0 (~~obviously~~).~~<br>~~	+	Adopt the following script to your needs:
-	MAC address of the box is "ABCDEF123456" ~~(or~~ "AB:CD:EF:12:34:56" ~~if you~~ are ~~used to the Windows format~~)~~.<br>~~	+	* Set `bcast_addr` to the broadcast address for you network segment.
-	The ~~LS has the~~ IP address of ~~10.131.200.1 (this IP address~~ is not ~~necessary~~ in the code!).	+	** In the example is is a private class B network 10.131/24 (10.131.0.0 - 10.131.255.255, netmask 255.255.0.0)
-	#!/usr/bin/env python	+	** If your netmask is /24 (255.255.255.0), you have to replace "10.131.255" with the first three numbers of your network segment.
-	import socket	+	* Set `target_mac` to the MAC address of the box you want to wake up. Colons are optional, case does not matter. So "ABCDEF123456" and "ab:cd:ef:12:34:56" are oth valid)
-	import time	+	* The IP-address of your LS is not relevant in the code, but the MAC is.
-	s=socket.socket(socket.AF_INET, socket.SOCK_DGRAM)	+
-	s.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)	+	#!/usr/bin/env python
-	while 1:	+	import socket
-	s.sendto(~~'\xff'6+'\xAB\xCD\xEF\x12\x34\x56'16~~, (~~'10.131.255.255'~~, 9))	+	import time
		+
		+	bcast_addr = '10.131.255.255' # broadcast address for you network
		+	target_mac = "ab:cd:ef:12:34:56" # colons are optional, case does not matter
		+
		+	mac = target_mac.replace(':', '')
		+	mac_bytes = ''.join([chr(int(mac[i:i+2], 16)) for i in range(0, len(mac), 2)])
		+	WoL_packet = '\xff'6 + mac_bytes 16
		+
		+	s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
		+	s.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
		+
		+	while 1:
		+	s.sendto(WoL_packet, (bcast_addr, 9))
	print "Sent paket!"		print "Sent paket!"
	time.sleep(180)		time.sleep(180)
-	~~If your netmask is 255.255.255.0, you have to replace "10.131.255" with the first three numbers of your network segment.<br><br>~~	+
-	You can put the code example just into a file and start the python interpreter by hand providing the file as parameter or execute the file as a shell script (on UNIXoid systems like LINUX, Mac OS X, FreeBSD etc.).~~<br>~~	+	You can put the code example just into a file and start the python interpreter by hand providing the file as parameter or execute the file as a shell script (on UNIXoid systems like LINUX, Mac OS X, FreeBSD etc.).
		+
	On an Enigma2 Dreambox or Mac OS X you will have a python interpreter within the default installation of the system. Other systems may need an installation of the python package beforehand.		On an Enigma2 Dreambox or Mac OS X you will have a python interpreter within the default installation of the system. Other systems may need an installation of the python package beforehand.

Lsuser1985: /* How to keep a box alive without a client in "auto" mode? */ minor cleaon to shell-script

Lsuser1985 — Fri, 18 Jan 2013 14:28:39 GMT

How to keep a box alive without a client in "auto" mode?: minor cleaon to shell-script

← Older revision		Revision as of 14:28, 18 January 2013
Line 14:		Line 14:
	Then start this script as a background task (means: add a " &" when calling the script):		Then start this script as a background task (means: add a " &" when calling the script):
	#!/bin/sh		#!/bin/sh
-	while [ -f /var/lock/kenatonline ];	+	while [ -f /var/lock/kenatonline ] ; do
-	do	+
	/usr/local/sbin/pwrmgr -c localhost act		/usr/local/sbin/pwrmgr -c localhost act
	sleep 180		sleep 180

Kenatonline: Python example for a wake up and keep alive of a box

Kenatonline — Sat, 29 Oct 2011 13:47:43 GMT

Python example for a wake up and keep alive of a box

← Older revision		Revision as of 13:47, 29 October 2011
Line 24:		Line 24:
	Of course this will only work, if the long time task is synchronous itself (means: the long time task is blocking the user input until it has finished).<br>		Of course this will only work, if the long time task is synchronous itself (means: the long time task is blocking the user input until it has finished).<br>
	Is it asynchronous, you have to find the postcondition which is true when the task finished and replace the while condition of the script above (e.g. testing for the process of the long time task).		Is it asynchronous, you have to find the postcondition which is true when the task finished and replace the while condition of the script above (e.g. testing for the process of the long time task).
		+
		+	== How to wake up and keep a box alive without using Buffalos applications? ==
		+	Not everyone likes to use the utilities Buffalo provided (if they are available for the intended target operating system at all).<br>
		+	=== Python ===
		+	Network is a private class B network (10.131.0.0 - 10.131.255.255), netmask is 255.255.0.0 (obviously).<br>
		+	MAC address of the box is "ABCDEF123456" (or "AB:CD:EF:12:34:56" if you are used to the Windows format).<br>
		+	The LS has the IP address of 10.131.200.1 (this IP address is not necessary in the code!).
		+	#!/usr/bin/env python
		+	import socket
		+	import time
		+	s=socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
		+	s.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
		+	while 1:
		+	s.sendto('\xff'6+'\xAB\xCD\xEF\x12\x34\x56'16, ('10.131.255.255', 9))
		+	print "Sent paket!"
		+	time.sleep(180)
		+	If your netmask is 255.255.255.0, you have to replace "10.131.255" with the first three numbers of your network segment.<br><br>
		+	You can put the code example just into a file and start the python interpreter by hand providing the file as parameter or execute the file as a shell script (on UNIXoid systems like LINUX, Mac OS X, FreeBSD etc.).<br>
		+	On an Enigma2 Dreambox or Mac OS X you will have a python interpreter within the default installation of the system. Other systems may need an installation of the python package beforehand.

	[[Category:LS-CHLv2]]		[[Category:LS-CHLv2]]

Kenatonline at 08:12, 19 March 2011

Kenatonline — Sat, 19 Mar 2011 08:12:52 GMT

← Older revision		Revision as of 08:12, 19 March 2011
Line 1:		Line 1:
-	== How to keep a box alive without a client if "auto" mode ~~is on~~ ? ==	+	== How does the "auto" mode work? ==
		+	There is a process running, waiting for WoL packets to arrive.<br>
		+	This process can be found as "pwrmgr" in the process list.<br>
		+	In addition to this, there is a script "/usr/local/sbin/pmcd_exec.sh" which uses a feature of the pwrmgr to keep the box alive even if there is no client anymore (e.g. in case of running backups, RAID recovery, running disk format etc.).
		+
		+	== How to keep a box alive without a client in "auto" mode? ==
	Sometimes one wants to keep the box alive until a script running on the box finished a long time task.<br>		Sometimes one wants to keep the box alive until a script running on the box finished a long time task.<br>
	If the box is running in "auto" mode (means: staying alive until the last client stops sending WoL packets),		If the box is running in "auto" mode (means: staying alive until the last client stops sending WoL packets),
-	one just has to call the next line once every 3 minutes:	+	one just has to call the next line once every 3 minutes to keep the box alive:
	pwrmgr -c localhost act		pwrmgr -c localhost act
		+	But how to use this, if the long time task takes more than 3 minutes to finish?<br>
		+	Before starting the long time task, create a file in /var/lock/ you can test for existance:
		+	touch /var/lock/kenatonline
		+	Then start this script as a background task (means: add a " &" when calling the script):
		+	#!/bin/sh
		+	while [ -f /var/lock/kenatonline ];
		+	do
		+	/usr/local/sbin/pwrmgr -c localhost act
		+	sleep 180
		+	done
		+	After the long time task, delete the file:
		+	rm /var/lock/kenatonline
		+	The box will shutdown automatically within 3 minutes.<br>
		+	Of course this will only work, if the long time task is synchronous itself (means: the long time task is blocking the user input until it has finished).<br>
		+	Is it asynchronous, you have to find the postcondition which is true when the task finished and replace the while condition of the script above (e.g. testing for the process of the long time task).

	[[Category:LS-CHLv2]]		[[Category:LS-CHLv2]]

Kenatonline at 07:47, 19 March 2011

Kenatonline — Sat, 19 Mar 2011 07:47:35 GMT

← Older revision		Revision as of 07:47, 19 March 2011
Line 4:		Line 4:
	one just has to call the next line once every 3 minutes:		one just has to call the next line once every 3 minutes:
	pwrmgr -c localhost act		pwrmgr -c localhost act
		+
		+	[[Category:LS-CHLv2]]
		+	[[Category:LS-XHL]]
		+	[[Category:LS-VL]]
		+	[[Category:LS-WXL]]
		+	[[Category:LS-WSXL]]
		+	[[Category:LS-WVL]]

Kenatonline: Compilation of useful informations on 'X' and 'V' series boxes not mentioned anywhere else in the wiki

Kenatonline — Sat, 19 Mar 2011 07:46:44 GMT

Compilation of useful informations on 'X' and 'V' series boxes not mentioned anywhere else in the wiki

New page

== How to keep a box alive without a client if "auto" mode is on ? ==
Sometimes one wants to keep the box alive until a script running on the box finished a long time task.<br>
If the box is running in "auto" mode (means: staying alive until the last client stops sending WoL packets),
one just has to call the next line once every 3 minutes:
pwrmgr -c localhost act