Amahi Wiki - User contributions [en]

Enabling WOL

2011-10-22T04:21:53Z

Ghstryder:

To enable Wake-On-Lan (WOL) on your HDA

1. Enable WOL in the BIOS

2. Boot Fedora. Open a terminal and execute <code>su</code> to get root access

3. Assuming your LAN interface is on eth0, run <code>ethtool eth0</code>

The output will look similar to this:

{{code|
[root@localhost ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
}}

4. Look for a line similar to this:

Wake-on: g

This means that WOL by magic packets is enabled on that interface.

If the line is

Wake-on: d

then WOL is disabled. Activate it by running <code>ethtool -s eth0 wol g</code>

If you don't find any line containing Wake-on at all, then your interface card doesn't support WOL, or the OS cannot detect it , or it's not enabled in the BIOS.

Check the ethtool man pages for a full explanation of the Wake-on options

* Note: Some legacy drivers forget the setting during boot. Run <code>ethtool eth0</code> again if you suspect this is the case

* Reference: See this link http://www.energystar.gov/index.cfm?c=power_mgt.pr_power_mgt_wol for a general explanation of WOL.

Linux-hda commands

2011-09-15T03:49:47Z

Ghstryder:

= Linux Basic Commands =
[[Basics|Linux Basic Commands]] most users will need.

= General Linux/HDA Commands =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>service httpd start</td>
<td>restart web server</td>
</tr>
<tr>
<td>yum -y update</td>
<td>automatically update fedora</td>
</tr>
<tr>
<td>rpm -Uvh http://dl.getdropbox.com/u/364883/Amahi/hda-platform-*.*-*.noarch.rpm</td>
<td>updates HDA</td>
</tr>
<tr>
<td>rpm -q hda-platform</td>
<td>check to see what version of HDA you're running</td>
</tr>
</table><br />

= HDA Script Commands =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>first-admin</td>
<td>returns name of first admin user</td>
</tr>
<tr>
<td>reset-user-password</td>
<td>reset a forgotten user password</td>
</tr>
</table>

'''NOTE:''' Must be run from the '''''/var/hda/platform/html/script''''' directory.

<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>hda-change-gw</td>
<td>change gateway/router IP address</td>
</tr>
<tr>
<td>hda-change-dns</td>
<td>change DNS provider for HDA</td>
</tr>
<tr>
<td>
hda-install-gem</td>
<td>install a specific Ruby Gem</td>
</tr>
<tr>
<td>hda-create-db-and-user</td>
<td>create MySql user and database</td>
</tr>
<tr>
<td>hda-new-install</td>
<td>manual install for Amahi</td>
</tr>
<tr>
<td>hda-php-zone-change</td>
<td>change time zone</td>
</tr>
<tr>
<td>hda-refresh-shares</td>
<td>refresh HDA shares</td>
</tr>
</table>

'''NOTE:''' Can be run from anywhere (located in '''/usr/bin''').

= Miscellaneous =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>service amahi-ushare restart</td>
<td>restart ushare after adding new content</td>
</tr>
<tr>
<td>vncserver</td>
<td>Starts the VNCServer</td>
</tr>
<tr>
<td>vncserver -kill :1</td>
<td>Stops the VNCServer</td>
</tr>
<tr>
<td>/etc/init.d/mt-daapd start</td>
<td>Starts mt-daapd</td>
</tr>
<tr>
<td>/etc/init.d/mt-daapd stop</td>
<td>Stops mt-daapd</td>
</tr>
<tr>
<td>e2fsck -c /dev/sdb1</td>
<td>Check hard drive sdb1 for errors</td>
</tr>
</table><br />

= Greyhole =
Use just "greyhole" in a Terminal to get the list, since those could change in the future. Currently, they are:
Usage: greyhole [ACTION] [OPTIONS]

Where ACTION is one of:
-?, --help Display this help and exit.
-D, --daemon Start the daemon.
-f, --fsck Schedule a fsck.
-l, --balance Balance available space on storage pool devices.
-s, --stats Display storage pool statistics.
-S, --status Display what the Greyhole daemon is currently doing.
-q, --view-queue Display the current work queue.
-a, --empty-attic Empty the attic.
-b, --debug=filename Debug past file operations.
-p, --prerotate Pre-rotate task (for logrotate).
-P, --postrotate Post-rotate task (for logrotate).
-t, --thaw[=path] Thaw a frozen directory. Greyhole will start working on
files inside <path>. If you don't supply an option, the list
of frozen directories will be displayed.
-w, --wait-for[=path] Tell Greyhole that the missing drive at <path> will return
soon, and that it shouldn't re-create additional file copies
to replace it. If you don't supply an option, the available
options (paths) will be displayed.
-g, --gone[=path] Tell Greyhole that the missing drive at <path> is gone for
good. Greyhole will start replacing the missing file copies
instantly. If you don't supply an option, the available
options (paths) will be displayed.
-n, --going[=path] Tell Greyhole that you want to remove a drive. Greyhole will
then make sure you don't loose any files, and that the
correct number of file copies are created to replace the
missing drive. If you don't supply an option, the available
options (paths) will be displayed.

For --fsck, the available OPTIONS are:
-e, --email-report Send an email when fsck completes, to report on what was
checked, and any error that was found.
-y, --dont-walk-graveyard
Speed up fsck by skipping the scan of the graveyard
directories. Scanning the graveyards is only required to
re-create symbolic links that might be missing from your
shared directories.
-c, --if-conf-changed Only fsck if greyhole.conf changed since the last fsck.
Used in the daily cron to prevent unneccesary fsck runs.
-d, --dir=path Only scan a specific directory, and all sub-directories.
The specified directory should be a Samba share, or a
sub-directory of a Samba share.

VNC

2011-04-20T04:34:26Z

Ghstryder:

<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NOTE: there is now a one-click [http://www.amahi.org/apps/vnc VNC App]'''
</div>

= Using VNC to use a remote desktop in the HDA =

Using [http://realvnc.com/ VNC] is useful if:

* You would like a Linux desktop to the HDA remotely
* You run your HDA headless (no monitor) and like to still use a desktop in it
* You would like to use a GUI to configure printer(s) or have a scanner or other device that requires a desktop program to configure and the machine is headless

= What you need =

* A server
* A client

= Client: Installation =

Download the client software and install:

* Windows: [http://realvnc.com RealVNC], [http://www.uvnc.com UltraVNC], [http://www.tightvnc.com TightVNC]
* MAC: [http://cotvnc.sourceforge.net/ Chicken of the VNC] - do not use the internal vnc client because there are some problems
* For Linux, you have the vncviewer package, available in most, if not all distros. For Fedora 12, do the following as [Open_Terminal_as_root|'''root'''] user:
yum -y install tigervnc

= Server Installation =

There are various ways to get the server going in your HDA. All of them require the server software.
# [http://www.amahi.org/apps/VNC VNC]: one-click install
# Manually as described below (notes may require some revision)

=== Manual Install ===
* As root, install the server:

yum -y install tigervnc-server

== Method 1 ==
* Open a terminal, become root and install the VNC server (tigervnc-server) as stated in the Manual Install section.
When the install has completed, press ctrl-D to end the root session. Leave the terminal open, or open one now.

*The following commands are entered as '''User'''.

* Type vncpasswd and press enter.
The system will prompt you for a password. Type a password and press the enter key.
The system will prompt you to verify the password. Type the password a second time and press the enter key.

* Type vncserver and press the enter key. The system will create the configuration files. You should see output similar to this:
xauth: creating new authority file /home/user/.xauthority
New 'host.localdomain:1 (user)' desktop is host.localdomain:1
Creating default startup script /home/user/.vnc/xstartup
Starting applications specified in /home/user/.xauthority
Log file is /home/user/.vnc/host.localdomain:1.log

* You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "user" is shown, you need to enter your user name.

* Type nano /home/user/.vnc/xstartup and press the enter key. Nano will open the file.
Find the following line:
twm &
Change that line to read:
exec gnome-session &
This change will open the VNC display with a Gnome desktop, even if the server is starting in Init 3 by default.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

*The following commands are entered as '''Root'''.

* Type su and press the enter key followed by the root password

You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "username" is shown, you need to enter your user name.

* Type nano /etc/sysconfig/vncservers and press the enter key. Nano will open the file.
Find the following lines:
'#' VNCSERVERS="1:username"
'#' VNCSERVERARGS[1]="-geometry 800x600 -nolisten tcp -localhost"

* Uncomment both lines by removing the # at the beginning of the lines.
Edit the lines so they appear as follows:
VNCSERVERS="1:username"
VNCSERVERARGS[1]="-geometry 1024x768 -nolisten tcp"
Enter your username in place of "username". After "geometry", you can enter any resolution you desire. You can come back and change this if necessary.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

* Finally, type chkconfig vncserver on and press the enter key. This will make the VNC server start when the computer starts.

* Press ctrl-D to end the root session, and then press ctrl-D again to close the terminal.

* That's it - Run your VNC Client and enter hda:1 as the host/IP address. You should now see your HDA Desktop screen.
*If you are interested in more security for your VNC connection, check the link listed below under "General Instructions"

* Repeat the configuration for each user you wish to be able to connect via VNC.
* Note you can have displays for users 1-9 and each will connect to their VNC session at port 590n (some VNC clients 'know' the 590 part and only have you enter n). Make certain that you have forwarded the correct port(s), or the range 5901 through 5909.
* Add -localhost to options if you are connecting through a ssh tunnel or only locally. This adds some security.

== Method 2 ==
* To start the server in your HDA, you need install tigervnc-server rpm package:
* From the '''root''' user:
yum -y install xinetd
chkconfig vncserver off
service vncserver stop
* Create /etc/gdm/custom.conf file and add the following:
#GDM configuration storage
[xdmcp]
Enable=true
[chooser]
[security]
DisallowTCP=false
[debug]
* Create /etc/xinetd.d/vnc1024 file and add the following (you can change the screen resolution by changing the geometry setting):
service vnc1024
{
disable = no
socket_type = stream
protocol = tcp
group = tty
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024×768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none
}
* Edit /etc/services and comment out the two lines as listed below:
#vnc-server 5900/tcp # VNC Server
#vnc-server 5900/udp # VNC Server
* Add this line below the two lines you commented out and save the changes:
vnc1024 5900/tcp # VNC and GDM
* Now restart the xinetd service
service xinetd restart
* Run your VNC Client and enter your HDA IP address for host/IP address. You should now see your HDA Desktop login screen. If you don't see the login screen, a reboot of the HDA may be required. This can be done via the dashboard or by executing the following as '''root''' user:
reboot now

== Method 3 (the cpg method) ==

* Every time the HDA is rebooted, when VNC is needed, ssh to the HDA
* The first time without do:
vncserver -geometry 1550x1100
* After the first time, I type vncs. I have an alias in ~/.bashrc:
alias vncs='vncserver -geometry 1550x1100 &> /dev/null &';

Notes:

* Why that resolution? That fits my monitors with the VNC window and frame enough to not display scrollbars and move around nicely. Change at will!
* It does involve the dreaded CLI.
* Since my HDA does not get rebooted often, this is not a huge problem

= General Instructions =

More detailed instructions are available [http://www.g-loaded.eu/2005/11/10/configure-vnc-server-in-fedora/ here].

= Troubleshooting for Vista =

This helpful page has helped with [http://www.windowsreference.com/internet-explorer/windows-has-blocked-this-software-because-it-cant-verify-the-publisher/ blocking VNC]

= Images for the App =
[[Image:VNC-logo.png]]
[[Image:VNC-sshot.png]]

VNC

2011-04-01T21:58:01Z

Ghstryder:

<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NOTE: there is now a one-click [http://www.amahi.org/apps/vnc VNC App]'''
</div>

= Using VNC to use a remote desktop in the HDA =

Using [http://realvnc.com/ VNC] is useful if:

* You would like a Linux desktop to the HDA remotely
* You run your HDA headless (no monitor) and like to still use a desktop in it
* You would like to use a GUI to configure printer(s) or have a scanner or other device that requires a desktop program to configure and the machine is headless

= What you need =

* A server
* A client

= Client: Installation =

Download the client software and install:

* Windows: [http://realvnc.com RealVNC], [http://www.uvnc.com UltraVNC], [http://www.tightvnc.com TightVNC]
* MAC: [http://cotvnc.sourceforge.net/ Chicken of the VNC] - do not use the internal vnc client because there are some problems
* For Linux, you have the vncviewer package, available in most, if not all distros. For Fedora 12, do the following as [Open_Terminal_as_root|'''root'''] user:
yum -y install tigervnc

= Server Installation =

There are various ways to get the server going in your HDA. All of them require the server software.
# [http://www.amahi.org/apps/VNC VNC]: one-click install
# Manually as described below (notes may require some revision)

=== Manual Install ===
* As root, install the server:

yum -y install tigervnc-server

== Method 1 ==
* Open a terminal, become root and install the VNC server (tigervnc-server) as stated in the Manual Install section.
When the install has completed, press ctrl-D to end the root session. Leave the terminal open, or open one now.

*The following commands are entered as '''User'''.

* Type vncpasswd and press enter.
The system will prompt you for a password. Type a password and press the enter key.
The system will prompt you to verify the password. Type the password a second time and press the enter key.

* Type vncserver and press the enter key. The system will create the configuration files. You should see output similar to this:
xauth: creating new authority file /home/user/.xauthority
New 'host.localdomain:1 (user)' desktop is host.localdomain:1
Creating default startup script /home/user/.vnc/xstartup
Starting applications specified in /home/user/.xauthority
Log file is /home/user/.vnc/host.localdomain:1.log

* You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "user" is shown, you need to enter your user name.

* Type nano /home/user/.vnc/xstartup and press the enter key. Nano will open the file.
Find the following line:
twm &
Change that line to read:
exec gnome-session &
This change will open the VNC display with a Gnome desktop, even if the server is starting in Init 3 by default.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

*The following commands are entered as '''Root'''.

* Type su and press the enter key followed by the root password

You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "username" is shown, you need to enter your user name.

* Type nano /etc/sysconfig/vncservers and press the enter key. Nano will open the file.
Find the following lines:
'#' VNCSERVERS="1:username"
'#' VNCSERVERARGS[1]="-geometry 800x600 -nolisten tcp -localhost"

* Uncomment both lines by removing the # at the beginning of the lines.
Edit the lines so they appear as follows:
VNCSERVERS="1:username"
VNCSERVERARGS[1]="-geometry 1024x768 -nolisten tcp"
Enter your username in place of "username". After "geometry", you can enter any resolution you desire. You can come back and change this if necessary.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

* Finally, type chkconfig vncserver on and press the enter key. This will make the VNC server start when the computer starts.

* Press ctrl-D to end the root session, and then press ctrl-D again to close the terminal.

* That's it - Run your VNC Client and enter hda:1 as the host/IP address. You should now see your HDA Desktop screen.
*If you are interested in more security for your VNC connection, check the link listed below under "General Instructions"

* Repeat the configuration for each user you wish to be able to connect via VNC.
* Note you can have displays for users 1-9 and each will connect to their VNC session at port 590n (some VNC clients 'know' the 590 part and only have you enter n)
* Add -localhost to options if you are connecting through a ssh tunnel or only locally. This adds some security.

== Method 2 ==
* To start the server in your HDA, you need install tigervnc-server rpm package:
* From the '''root''' user:
yum -y install xinetd
chkconfig vncserver off
service vncserver stop
* Create /etc/gdm/custom.conf file and add the following:
#GDM configuration storage
[xdmcp]
Enable=true
[chooser]
[security]
DisallowTCP=false
[debug]
* Create /etc/xinetd.d/vnc1024 file and add the following (you can change the screen resolution by changing the geometry setting):
service vnc1024
{
disable = no
socket_type = stream
protocol = tcp
group = tty
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024×768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none
}
* Edit /etc/services and comment out the two lines as listed below:
#vnc-server 5900/tcp # VNC Server
#vnc-server 5900/udp # VNC Server
* Add this line below the two lines you commented out and save the changes:
vnc1024 5900/tcp # VNC and GDM
* Now restart the xinetd service
service xinetd restart
* Run your VNC Client and enter your HDA IP address for host/IP address. You should now see your HDA Desktop login screen. If you don't see the login screen, a reboot of the HDA may be required. This can be done via the dashboard or by executing the following as '''root''' user:
reboot now

== Method 3 (the cpg method) ==

* Every time the HDA is rebooted, when VNC is needed, ssh to the HDA
* The first time without do:
vncserver -geometry 1550x1100
* After the first time, I type vncs. I have an alias in ~/.bashrc:
alias vncs='vncserver -geometry 1550x1100 &> /dev/null &';

Notes:

* Why that resolution? That fits my monitors with the VNC window and frame enough to not display scrollbars and move around nicely. Change at will!
* It does involve the dreaded CLI.
* Since my HDA does not get rebooted often, this is not a huge problem

= General Instructions =

More detailed instructions are available [http://www.g-loaded.eu/2005/11/10/configure-vnc-server-in-fedora/ here].

= Troubleshooting for Vista =

This helpful page has helped with [http://www.windowsreference.com/internet-explorer/windows-has-blocked-this-software-because-it-cant-verify-the-publisher/ blocking VNC]

= Images for the App =
[[Image:VNC-logo.png]]
[[Image:VNC-sshot.png]]

VNC

2011-04-01T21:57:12Z

Ghstryder:

<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NOTE: there is now a one-click [http://www.amahi.org/apps/vnc VNC App]'''
</div>

= Using VNC to use a remote desktop in the HDA =

Using [http://realvnc.com/ VNC] is useful if:

* You would like a Linux desktop to the HDA remotely
* You run your HDA headless (no monitor) and like to still use a desktop in it
* You would like to use a GUI to configure printer(s) or have a scanner or other device that requires a desktop program to configure and the machine is headless

= What you need =

* A server
* A client

= Client: Installation =

Download the client software and install:

* Windows: [http://realvnc.com RealVNC], [http://www.uvnc.com UltraVNC], [http://www.tightvnc.com TightVNC]
* MAC: [http://cotvnc.sourceforge.net/ Chicken of the VNC] - do not use the internal vnc client because there are some problems
* For Linux, you have the vncviewer package, available in most, if not all distros. For Fedora 12, do the following as [Open_Terminal_as_root|'''root'''] user:
yum -y install tigervnc

= Server Installation =

There are various ways to get the server going in your HDA. All of them require the server software.
# [http://www.amahi.org/apps/VNC VNC]: one-click install
# Manually as described below (notes may require some revision)

=== Manual Install ===
* As root, install the server:

yum -y install tigervnc-server

== Method 1 ==
* Open a terminal, become root and install the VNC server (tigervnc-server) as stated in the Manual Install section.
When the install has completed, press ctrl-D to end the root session. Leave the terminal open, or open one now.

*The following commands are entered as '''User'''.

* Type vncpasswd and press enter.
The system will prompt you for a password. Type a password and press the enter key.
The system will prompt you to verify the password. Type the password a second time and press the enter key.

* Type vncserver and press the enter key.
The system will create the configuration files. You should see output similar to this:
xauth: creating new authority file /home/user/.xauthority
New 'host.localdomain:1 (user)' desktop is host.localdomain:1
Creating default startup script /home/user/.vnc/xstartup
Starting applications specified in /home/user/.xauthority
Log file is /home/user/.vnc/host.localdomain:1.log

* You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "user" is shown, you need to enter your user name.

* Type nano /home/user/.vnc/xstartup and press the enter key. Nano will open the file.
Find the following line:
twm &
Change that line to read:
exec gnome-session &
This change will open the VNC display with a Gnome desktop, even if the server is starting in Init 3 by default.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

*The following commands are entered as '''Root'''.

* Type su and press the enter key followed by the root password

You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "username" is shown, you need to enter your user name.

* Type nano /etc/sysconfig/vncservers and press the enter key. Nano will open the file.
Find the following lines:
'#' VNCSERVERS="1:username"
'#' VNCSERVERARGS[1]="-geometry 800x600 -nolisten tcp -localhost"

* Uncomment both lines by removing the # at the beginning of the lines.
Edit the lines so they appear as follows:
VNCSERVERS="1:username"
VNCSERVERARGS[1]="-geometry 1024x768 -nolisten tcp"
Enter your username in place of "username". After "geometry", you can enter any resolution you desire. You can come back and change this if necessary.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

* Finally, type chkconfig vncserver on and press the enter key. This will make the VNC server start when the computer starts.

* Press ctrl-D to end the root session, and then press ctrl-D again to close the terminal.

* That's it - Run your VNC Client and enter hda:1 as the host/IP address. You should now see your HDA Desktop screen.
*If you are interested in more security for your VNC connection, check the link listed below under "General Instructions"

* Repeat the configuration for each user you wish to be able to connect via VNC.
* Note you can have displays for users 1-9 and each will connect to their VNC session at port 590n (some VNC clients 'know' the 590 part and only have you enter n)
* Add -localhost to options if you are connecting through a ssh tunnel or only locally. This adds some security.

== Method 2 ==
* To start the server in your HDA, you need install tigervnc-server rpm package:
* From the '''root''' user:
yum -y install xinetd
chkconfig vncserver off
service vncserver stop
* Create /etc/gdm/custom.conf file and add the following:
#GDM configuration storage
[xdmcp]
Enable=true
[chooser]
[security]
DisallowTCP=false
[debug]
* Create /etc/xinetd.d/vnc1024 file and add the following (you can change the screen resolution by changing the geometry setting):
service vnc1024
{
disable = no
socket_type = stream
protocol = tcp
group = tty
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024×768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none
}
* Edit /etc/services and comment out the two lines as listed below:
#vnc-server 5900/tcp # VNC Server
#vnc-server 5900/udp # VNC Server
* Add this line below the two lines you commented out and save the changes:
vnc1024 5900/tcp # VNC and GDM
* Now restart the xinetd service
service xinetd restart
* Run your VNC Client and enter your HDA IP address for host/IP address. You should now see your HDA Desktop login screen. If you don't see the login screen, a reboot of the HDA may be required. This can be done via the dashboard or by executing the following as '''root''' user:
reboot now

== Method 3 (the cpg method) ==

* Every time the HDA is rebooted, when VNC is needed, ssh to the HDA
* The first time without do:
vncserver -geometry 1550x1100
* After the first time, I type vncs. I have an alias in ~/.bashrc:
alias vncs='vncserver -geometry 1550x1100 &> /dev/null &';

Notes:

* Why that resolution? That fits my monitors with the VNC window and frame enough to not display scrollbars and move around nicely. Change at will!
* It does involve the dreaded CLI.
* Since my HDA does not get rebooted often, this is not a huge problem

= General Instructions =

More detailed instructions are available [http://www.g-loaded.eu/2005/11/10/configure-vnc-server-in-fedora/ here].

= Troubleshooting for Vista =

This helpful page has helped with [http://www.windowsreference.com/internet-explorer/windows-has-blocked-this-software-because-it-cant-verify-the-publisher/ blocking VNC]

= Images for the App =
[[Image:VNC-logo.png]]
[[Image:VNC-sshot.png]]

VNC

2011-03-29T03:35:50Z

Ghstryder: Updated Method 1

<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NOTE: there is now a one-click [http://www.amahi.org/apps/vnc VNC App]'''
</div>

= Using VNC to use a remote desktop in the HDA =

Using [http://realvnc.com/ VNC] is useful if:

* You would like a Linux desktop to the HDA remotely
* You run your HDA headless (no monitor) and like to still use a desktop in it
* You would like to use a GUI to configure printer(s) or have a scanner or other device that requires a desktop program to configure and the machine is headless

= What you need =

* A server
* A client

= Client: Installation =

Download the client software and install:

* Windows: [http://realvnc.com RealVNC], [http://www.uvnc.com UltraVNC], [http://www.tightvnc.com TightVNC]
* MAC: [http://cotvnc.sourceforge.net/ Chicken of the VNC] - do not use the internal vnc client because there are some problems
* For Linux, you have the vncviewer package, available in most, if not all distros. For Fedora 12, do the following as [Open_Terminal_as_root|'''root'''] user:
yum -y install tigervnc

= Server Installation =

There are various ways to get the server going in your HDA. All of them require the server software.
# [http://www.amahi.org/apps/VNC VNC]: one-click install
# Manually as described below (notes may require some revision)

=== Manual Install ===
* As root, install the server:

yum -y install tigervnc-server

== Method 1 ==
* Open a terminal, become root and install the VNC server (tigervnc-server) as stated in the Manual Install section.
When the install has completed, press ctrl-D to end the root session. Leave the terminal open, or open one now.

*The following commands are entered as '''User'''.

* Type vncpasswd and press enter.
The system will prompt you for a password. Type a password and press the enter key.
The system will prompt you to verify the password. Type the password a second time and press the enter key.

* Type vncserver and press the enter key.
The system will create the configuration files. You should see output similar to this:
xauth: creating new authority file /home/user/.xauthority
New 'host.localdomain:1 (user)' desktop is host.localdomain:1
Creating default startup script /home/user/.vnc/xstartup
Starting applications specified in /home/user/.xauthority
Log file is /home/user/.vnc/host.localdomain:1.log

* You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "user" is shown, you need to enter your user name.

* Type nano /home/user/.vnc/xstartup and press the enter key. Nano will open the file.
Find the following line:
twm &
Change that line to read:
exec gnome-session &
This change will open the VNC display with a Gnome desktop, even if the server is starting in Init 3 by default.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

*The following commands are entered as '''Root'''.

* Type su and press the enter key followed by the root password

You can edit the configuration files using your choice of editor. Nano is used below.
Note that when "username" is shown, you need to enter your user name.

* Type nano /etc/sysconfig/vncservers and press the enter key. Nano will open the file.
Find the following lines:
'#' VNCSERVERS="1:username"
'#' VNCSERVERARGS[1]="-geometry 800x600 -nolisten tcp -localhost"

* Uncomment both lines by removing the # at the beginning of the lines.
Edit the lines so they appear as follows:
VNCSERVERS="1:username"
VNCSERVERARGS[1]="-geometry 1024x768 -nolisten tcp"
Enter your username in place of "username". After "geometry", you can enter any resolution you desire. You can come back and change this if necessary.
Press ctrl-X to exit Nano. You will see the prompt at the bottom "Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ?
Press the Y key. The prompt will change, showing you the file name.
Press the enter key, this will store your change and exit Nano.

* Finally, type chkconfig vncserver on and press the enter key. This will make the VNC server start when the computer starts.

* Press ctrl-D to end the root session, and then press ctrl-D again to close the terminal.

* That's it - Run your VNC Client and enter hda:1 as the host/IP address. You should now see your HDA Desktop screen.
*If you are interested in more security for your VNC connection, check the link listed below under "General Instructions"

* Repeat the configuration for each user you wish to be able to connect via VNC.
* Note you can have displays for users 1-9 and each will connect to their VNC session at port 590n (some VNC clients 'know' the 590 part and only have you enter n)
* Add -localhost to options if you are connecting through a ssh tunnel or only locally. This adds some security.

== Method 2 ==
* To start the server in your HDA, you need install tigervnc-server rpm package:
* From the '''root''' user:
yum -y install xinetd
chkconfig vncserver off
service vncserver stop
* Create /etc/gdm/custom.conf file and add the following:
#GDM configuration storage
[xdmcp]
Enable=true
[chooser]
[security]
DisallowTCP=false
[debug]
* Create /etc/xinetd.d/vnc1024 file and add the following (you can change the screen resolution by changing the geometry setting):
service vnc1024
{
disable = no
socket_type = stream
protocol = tcp
group = tty
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024×768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none
}
* Edit /etc/services and comment out the two lines as listed below:
#vnc-server 5900/tcp # VNC Server
#vnc-server 5900/udp # VNC Server
* Add this line below the two lines you commented out and save the changes:
vnc1024 5900/tcp # VNC and GDM
* Now restart the xinetd service
service xinetd restart
* Run your VNC Client and enter your HDA IP address for host/IP address. You should now see your HDA Desktop login screen. If you don't see the login screen, a reboot of the HDA may be required. This can be done via the dashboard or by executing the following as '''root''' user:
reboot now

== Method 3 (the cpg method) ==

* Every time the HDA is rebooted, when VNC is needed, ssh to the HDA
* The first time without do:
vncserver -geometry 1550x1100
* After the first time, I type vncs. I have an alias in ~/.bashrc:
alias vncs='vncserver -geometry 1550x1100 &> /dev/null &';

Notes:

* Why that resolution? That fits my monitors with the VNC window and frame enough to not display scrollbars and move around nicely. Change at will!
* It does involve the dreaded CLI.
* Since my HDA does not get rebooted often, this is not a huge problem

= General Instructions =

More detailed instructions are available [http://www.g-loaded.eu/2005/11/10/configure-vnc-server-in-fedora/ here].

= Troubleshooting for Vista =

This helpful page has helped with [http://www.windowsreference.com/internet-explorer/windows-has-blocked-this-software-because-it-cant-verify-the-publisher/ blocking VNC]

= Images for the App =
[[Image:VNC-logo.png]]
[[Image:VNC-sshot.png]]

Amahi Energy Saver

2011-03-11T16:53:37Z

Ghstryder: added .rb to ./aes --showenergybalance and ./aes --setpowerconsumption

[[Image:Amahi-Energy-Saver_Logo.png|150px]]<br>

==General==

This project is approaching beta. It runs fine on my machine, however I need more feedback from the community to be sure that it's stable enough for the general public. So, please test and report your experience!

==Introduction==
Running servers when they are not needed can waste a considerable amount of energy. This project aims at sending Amahi server to suspend or poweroff when not needed.

To do so, Amahi Energy Saver regularly scans for connected clients, which are defined in the "monitored host list". If none of these clients is turned on, the system suspends after a configurable period.

So, for instance, you may want to add your client PC and your PS3 to the monitored host list. The Amahi Box will then stay up and running as long as client PC and/or PS3 are up and running. However, you might not want to add your home router to the list, as the router is always turned on.

With the calendar fucntion one can define scheduled wake ups and periods during which the server shall stay awake no matter what.

Amahi Energy Saver also checks shares. As long as shares are accessed, the server does not suspend. If set up to do so, Squeezeboxserver is monitored to prevent suspend while Squeezeboxes are turned on.

When the system is to be used again, simply wake it up with WOL (ref. http://en.wikipedia.org/wiki/Wake-on-LAN). There are many tools to generate WOL packets, and it is even possible to wake your server over the internet (good link: http://www.wakeonlan.me/).

==Download==

Download the latest tested and released version here: http://code.google.com/p/amahienergysaver/downloads/list

Latest untested sources are available at Git:
https://github.com/jayrockk/Amahi-Energy-Saver

==Initial setup==

1. Copy the tar.gz file from the download page to some folder and unpack it with

{{Code|Code=
tar -zxf filename
}}

2. Open a terminal, change to that folder and get superuser rights by running <code>su</code>

3. As root, run
{{Code|Code=
./aes-install.sh
}}

4. Navigate to
{{Code|Code=
cd /usr/share/aes
}}
and run
{{Code|Code=
./aes.rb --shownetworkhosts
}}
to show and select to add any currently active network host to the list of monitored hosts. Run
{{Code|Code=
./aes.rb --showmonitoredhosts
}}
to check the monitored hosts and delete the ones you want to remove.

5. As root, run
{{Code|Code=
service aes start
}}
to start the service. Be careful, when you start the service the sytem MAY go to sleep when you don't expect it. Once it works as you want it, run
{{Code|Code=
chkconfig aes on
}}
to make the service start on boot.

==Integration with Amahi calendar==
1. Open a terminal on your hda.

2. Type
{{Code|Code=
su
}}
and provide your root password

3. Type
{{Code|Code=
cd /usr/share/aes
}}

4. Type
{{Code|Code=
./aes --calendar ical
}}

4b. To be sure, restart the service by typing
{{Code|Code=
service aes restart
}}

5. Only required for 0.3.6 and below: Open your HDA dashboard and go to "Settings" -> "Calendars".

6. Only required for 0.3.6 and below: Add a new calendar named <code>aes</code>

7. Connect your client to the new calendar. NOTE: Please read this article if you are unsure how to do this: [[Calendars]]

8. Use your favourite calendar client to populate the calendar with events.

Done! Your HDA will now wake up and stay powered on according to the events defined in the aes calendar.

==Command Line Interface==
*Note: Currently root privileges are required to execute the CLI command. Navigate to /usr/share/aes to use the CLI correctly.

{{Code|Code=
./aes.rb --shownetworkhosts
}}
Lists the hosts found in the network, ie, all devices connected to the network. Gives the user the choice to add hosts to the monitored host list.

{{Code|Code=
./aes.rb --showmonitoredhosts
}}
Show a list of all hosts which are monitored by AES (i.e. the monitored host list), and also allows to delete hosts from the list. If these hosts are up and running (and respond to ping), the server does not suspend.

{{Code|Code=
./aes.rb --addhost macadress
}}
Manually add a host to the monitored host list. Observe the MAC address format, which has to be XX:XX:XX:XX:XX:XX. Example is <br> <code>./aes.rb --addhost 12:34:56:78:90:ab</code>

{{Code|Code=
./aes.rb --calendar [off, internal, ical, debug]
}}
<code>./aes.rb --calendar</code> shows the current setting.
<code>./aes.rb --calendar off</code> turns the calendar off,
<code>./aes.rb --calendar internal</code> makes aes use its internal calendar function and
<code>./aes.rb --calendar ical</code> activates the Amahi calendar integration. To show diag information use <code>./aes.rb --calendar debug</code>

{{Code|Code=
./aes.rb --showcalendar
}}
Lists the current entries of the internal calendar. Calendar entries define times when the server does not suspend. Also, the server will be woken up at the beginning of a calendar entry.

{{Code|Code=
./aes.rb --addcalendar startdate starttime stopdate stoptime
}}
Use this command to add an entry to the internal calendar. Format of startdate/stopdate: YYYY-MM-DD Format of starttime/stoptime: hhm:mm. Eg.
<br><code>./aes.rb --addcalendar 2010-12-20 15:00 2010-12-20 16:00</code> <br>
will keep the server awake on Dec 20th, 2010 from 15 to 16 hrs (3 to 4 pm). The server will also wake up at 15 hrs if it is suspended.

{{Code|Code=
./aes.rb --shutdowntype
}}
Show and modifiy the type of shutdown. NOTE: Not all shutdown types may be supported on your system, or may work correctly. Therefore, test that your machine is suspending and coming up correctly before deciding for a setting. Poweroff is safest type.

{{Code|Code=
./aes.rb --sbs [on, off, debug]
}}
<code>./aes.rb --sbs</code> shows the current setting. <code>./aes.rb --sbs on</code> and <code>./aes.rb --sbs off</code> switch monitoring of Squeezeboxserver on or off, respectively. The command <code>./aes.rb --sbs debug</code> displays diagnostic information

{{Code|Code=
./aes.rb --interval
}}
aes checks regularly if the system can be suspended or shut down. This parameter specifies the time in seconds between two such checks. Normally should be left untouched.

{{Code|Code=
./aes.rb --showenergybalance
}}
View the energy savings in kWh due to the use of Amahi Energy Saver.

{{Code|Code=
./aes.rb --setpowerconsumption pc_on pc_standby
}}
Set the average power consumption when working ("pc_on") and powered off ("pc_standby"). Values given in Watts. pc_on must be greater than pc_standby.

{{Code|Code=
./aes.rb --help
}}
Displays command line help

==Selecting ShutdownType==

The different options for ShutdownType are explained here:<br><br>

Poweroff
This is a full shutdown and should work on most systems. Some mainboards do not allow scheduled wakeup when using this method.<br><br>

ACPI_S1
Legacy ACPI S1 state. Support depends on mainboard and Fedora support<br><br>

ACPI_S3
Legacy ACPI S3 state. Support depends on mainboard and Fedora support<br><br>

ACPI_S4
Legacy ACPI S4 state. Support depends on mainboard and Fedora support<br><br>

mem
Suspend to memory, is intended to replace ACPI S1 but is not widely supported yet<br><br>

disk
Suspend to disk, is intended to replace ACPI S4 but is not widely supported yet<br><br>

standby
Suspend to memory, is intended to replace ACPI S3 but is not widely supported yet<br><br>

When selecting the shutdown type the following procedure is suggested:<br><br>

* Start with Poweroff to do basic checking and configuration. Since this is the safest version, it should also be your resort in case of problems.<br><br>

* Once things are working, select either of the ACPI_S1..3 depending on what level of suspend you want<br><br>

* If you are brave or the ACPI options don't work, try mem, disk or standby.<br><br>

==Windows client==
On the download page there is a Windows client for automatic or manual wakeup of the HDA.

*Installation

Just run the msi file found on the download page. The client will be included in the startup folder.

*Configuration

1. Form the start menu, run AmahiEnergySaver -> AES Client

2. Right click on the icon that will appear in symbol bar, and select "Show config"

3. To get started, make sure that you set "Host MAC" and "Host name" to your HDA configuration. Hit "Select Server" to bring up the "Select HDA" window, and then "Search". If possible the correct server is alreday selected, in that case just hit "Ok" to confirm. Continue with 4.<br><br>
If the server appears on the list but is not automatically selected, click on it and hit return.<br><br>
Should your server not show up at all, press "Cancel" to exit the "Select HDA" dialog and configure MAC and host name manually.<br><br>
Finally, if requried, change the "Port" setting. The default "9" should work in most cases. <br><br>

4. Hit the "OK" butten, then right click on the symbol again, select "Exit" and and restart the program as described in 1.

5. Done! You should now be able to start your HDA by right clicking on the icon in the symbol bar and select "Wake now"

==Logs==
Logs are located in /usr/share/aes and named aes.log*