Amahi Wiki - User contributions [en]

Database Backup

2013-09-09T15:39:39Z

Peter Olson: added some whitespace

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
It's good practice to periodically backup up your database. This functionality is coming to Amahi soon, but until then there is a simple way to automate it. This can be done using [http://members.multimania.co.uk/wipe_out/automysqlbackup/ AutoMySQLBackup] script.
__NOTOC__
== Features ==
* Backup multiple MySQL databases with one script. (Now able to backup ALL databases on a server easily. no longer need to specify each database separately)
* Backup all databases to a single backup file or to a separate directory and file for each database.
* Automatically compress the backup files to save disk space using either gzip or bzip2 compression.
* Can backup remote MySQL servers to a central server.
* Runs automatically using cron or can be run manually.
* Can e-mail the backup log to any specified e-mail address instead of "root". (Great for hosted websites and databases).
* Can email the compressed database backup files to the specified email address.
* Can specify maximum size backup to email.
* Can be set to run PRE and POST backup commands.
* Choose which day of the week to run weekly backups.

== What it does ==
* Every day it will run mysqldump and gzip will dump your specified databases to the ''/var/hda/files/dbbackup/daily'' directory, it will rotate daily backups weekly so you should never have more than 7 backups in there.
* Every Saturday it will again backup the databases you have chosen but they will be placed into ''/var/hda/files/dbbackup/weekly'', these will be rotated every 5 weeks so there should never be more than 5 backups in there.
* Every 1st of the month it will create a backup of all databases and place them into ''/var/hda/files/dbbackup/monthly''. These will never be rotated so it will be up to you to do your own house keeping. I would suggest taking a copy of this offline every month or two so that if you have a hard drive failure you will be able to restore your database.

== How to Install ==
===In Ubuntu===
* install via apt-get
{{Code|sudo apt-get install automysqlbackup}}
* edit the config file located at {{Text|/etc/default/automysqlbackup}}
{{Code|sudo nano /etc/default/automysqlbackup}}
* At the bare minimun, in the config file, edit the BACKUPDIR variable
* run automysqlbackup to see if it works (you should get backups added to your backupdir directory:
{{Code|sudo automysqlbackup}}
* Edit cron:
{{Code|sudo crontab -e}}
* add the following for running cron everyday at midnight
{{Text|0 0 * * * /usr/sbin/automysqlbackup}}

===Installing from project file===
* Create a share called '''dbbackup'''.
* Download the script to ''/tmp'' directory.
{{Code|cd /tmp
wget http://downloads.sourceforge.net/project/automysqlbackup/AutoMySQLBackup/AutoMySQLBackup%20VER%202.5/automysqlbackup-2.5.1-01.sh}}
* Some changes will need to be made for this to work on your HDA. As '''root''' user, update lines indicated in ''automysqlbackup-2.5.1-01.sh'' to read as follows:
{{Text|Text=Line 39: USERNAME=root
Line 42: PASSWORD=hda
Line 51: BACKUPDIR="/var/hda/files/dbbackup"
Line 65: MAILADDR="root"
Line 76: DBEXCLUDE="information_schema performance_schema mysql"
Line 79: CREATE_DATABASE=yes
Line 94: LATEST=yes}}<br />

* Rename and copy the ''automysqlbackup-2.5.1-01.sh'' from ''/tmp'' to ''/usr/bin'' and set the permissions:
{{Code|cd /usr/bin
cp /tmp/automysqlbackup-2.5.1-01.sh automysqlbackup
chmod 755 automysqlbackup}}
* Set ''automysqlbackup'' as a daily cron job (Optional):
{{Code|cd /etc/cron.daily
ln -s /usr/bin/automysqlbackup}}

== Tips ==
* To change day of week (1=Monday thru 7=Sunday; defaults to 6=Saturday) for backup, update the number on the following line in ''automysqlbackup'' as '''root''' user:
{{Text|Text=Line 85: DOWEEKLY=6}}
* To run anytime, as root do the following:
{{Code|automysqlbackup}}
* This script is well documented. Options can be easily customized to meet your specific HDA requirements. The guidance can be found in the ''automysqlbackup'', starting at line 110.

'''NOTE:''' When it's run the first time, it will create the directory structure automatically if it does not already exist.

Database Backup

2013-09-09T15:36:33Z

Peter Olson: Added how to do this in ubuntu

Amahi Virtualized

2013-08-15T18:43:29Z

Peter Olson: fixed a link

[https://wiki.amahi.org/index.php/Main_Page#Installation Back to 'Main Page - Installation']
{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading = - PLEASE NOTE - |
message = This is recommended only for advanced users, proceed with caution.}}
<b><i>This section will document how to run an Amahi HDA in a virtual server environment and such related concepts.<br /></i></b>
<br />
<h3>Preliminary - Planning and Host Guidance</h3>
If you're about to embark on making a virtualization host computer for your Amahi server and other servers you wish to run on the same hardware, then please go ahead with this preliminary guide.<br />
If you already have a host or hypervisor setup and working, then you have a lot of work taken care of already, and you just need to read about whichever one is hosting your HDA. For this you should skip the shortlist below and go straight to the "Options: Amahi Virtualization" section.
<ol>
<li>Decide why you want to virtualize - while beneficial for having many servers and optimizing hardware usage, it does require more computer power and isn't always compatible with the things you might want to do with your VMs, such as CD-ROM pass-thru.</li>
<li>Gather quality hardware and check everything. Something as simple as a bad RAM stick will wreak havoc on your VMs.</li>
<li>Don't immediately move your production/important files or apps to your new VM. You must test for at least a day or so, and have a comfort level before relying on your VM inside your new virtualization host.</li>
<li>Decide ahead of time if you intend on using Greyhole drive pooling or not, with your Amahi VM. This will change how you, A) setup your hypervisor/host and, B) how you setup Amahi</li>
<li>Suggested hardware for a hypervisor to run at least 4 VMs would be<br />- quad-core CPU or more<br />- 8GB of RAM (gives room to grow)<br />- lots of storage, across several drives (consider your base OS, and then the VM images themselves, and possible additional storage images or entire drives)<br />- Gigabit NIC (at least one, strongly suggested at gigabit speeds to accommodate traffic from several VMs.</li>
</ol>
<br />
<h3>Options: Amahi virtualization...</h3>
<ul>
<li>inside <b>[http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html| Oracle Virtualbox] ([https://forums.virtualbox.org/ VirtualBox Forum])</b><br />
- [[Amahi_on_VirtualBox|Generic setup]]<br />
- with greyhole<br />
- without greyhole</li>
<li>inside <b>[http://www.proxmox.com/proxmox-ve Proxmox VE] ([http://forum.proxmox.com Proxmox Forum])</b><br />
- [[Amahi_in_Proxmox_with_Greyhole|with greyhole]]<br />
- [[Amahi_in_Proxmox_without_Greyhole|without greyhole]]</li>
<li>inside <b>[http://www.vmware.com/products/vsphere-hypervisor/overview.html VMware ESXi] ([http://communities.vmware.com/community/vmtn/server/vsphere ESXi5 Forum)]</b><br />
- with greyhole<br />
- without greyhole</li>
<li>inside <b>[http://www.xenproject.org/downloads/xen-cloud-platform-archives/xen-cloud-platform-16.html XCP] (no longer being developed), [http://xenserver.org/ Xenserver] (opensourced) & [http://www.citrix.com/products/xenserver/overview.html Citrix Xenserver] (Citrix and Opensource versions are the same thing as of 6.2 - ([http://xenproject.org/help/questions-and-answers.html Xenproject Q/A] or [http://forums.citrix.com/category.jspa?categoryID=101 Citrix Forums])</b><br />
- [[Amahi_in_Xenserver_with_Greyhole|with greyhole]]<br />
- without greyhole</li>
</ul>
<br />
<h3>Related Amahi Wiki Reference:</h3>
<ul>
<li>[[KVM Virtualization|KVM Virtualization in Linux (with lib-virt, etc)]]</li>
<li>[[KVM|Turning your current server into a KVM-capable host (also with lib-virt, etc)]]</li>
<li>[[Amahi_on_a_VM|Amahi in a VM (short intro)]]</li>
<li>[[VirtualBox|VirtualBox on a Fedora 12 Host]]</li>
<li>[[VMware_Server|Setup VMWare Server on a Fedora 14 host]]</li>
<li>[[PhpVirtualBox|Setup PHPVirtualBox - requires VirtualBox already setup]]</li>
<li><b>[https://forums.amahi.org/viewforum.php?f=41 Amahi Forums - Virtualization Section]</b></li>
</ul>
<br />
<h3>reference outside Amahi..</h3>
* [http://wiki.qemu.org/Qemu-doc.html QEMU Manual]
* [http://www.linux-kvm.org/page/Tuning_KVM Tuning KVM]
* [http://www.linux-kvm.org/page/Main_Page KVM / QEMU Wiki]
<br />
<br />
[[Category:Virtualization]]

Amahi Virtualized

2013-08-15T18:42:36Z

Peter Olson: Added xenserver links

[https://wiki.amahi.org/index.php/Main_Page#Installation Back to 'Main Page - Installation']
{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading = - PLEASE NOTE - |
message = This is recommended only for advanced users, proceed with caution.}}
<b><i>This section will document how to run an Amahi HDA in a virtual server environment and such related concepts.<br /></i></b>
<br />
<h3>Preliminary - Planning and Host Guidance</h3>
If you're about to embark on making a virtualization host computer for your Amahi server and other servers you wish to run on the same hardware, then please go ahead with this preliminary guide.<br />
If you already have a host or hypervisor setup and working, then you have a lot of work taken care of already, and you just need to read about whichever one is hosting your HDA. For this you should skip the shortlist below and go straight to the "Options: Amahi Virtualization" section.
<ol>
<li>Decide why you want to virtualize - while beneficial for having many servers and optimizing hardware usage, it does require more computer power and isn't always compatible with the things you might want to do with your VMs, such as CD-ROM pass-thru.</li>
<li>Gather quality hardware and check everything. Something as simple as a bad RAM stick will wreak havoc on your VMs.</li>
<li>Don't immediately move your production/important files or apps to your new VM. You must test for at least a day or so, and have a comfort level before relying on your VM inside your new virtualization host.</li>
<li>Decide ahead of time if you intend on using Greyhole drive pooling or not, with your Amahi VM. This will change how you, A) setup your hypervisor/host and, B) how you setup Amahi</li>
<li>Suggested hardware for a hypervisor to run at least 4 VMs would be<br />- quad-core CPU or more<br />- 8GB of RAM (gives room to grow)<br />- lots of storage, across several drives (consider your base OS, and then the VM images themselves, and possible additional storage images or entire drives)<br />- Gigabit NIC (at least one, strongly suggested at gigabit speeds to accommodate traffic from several VMs.</li>
</ol>
<br />
<h3>Options: Amahi virtualization...</h3>
<ul>
<li>inside <b>[http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html| Oracle Virtualbox] ([https://forums.virtualbox.org/ VirtualBox Forum])</b><br />
- [[Amahi_on_VirtualBox|Generic setup]]<br />
- with greyhole<br />
- without greyhole</li>
<li>inside <b>[http://www.proxmox.com/proxmox-ve Proxmox VE] ([http://forum.proxmox.com Proxmox Forum])</b><br />
- [[Amahi_in_Proxmox_with_Greyhole|with greyhole]]<br />
- [[Amahi_in_Proxmox_without_Greyhole|without greyhole]]</li>
<li>inside <b>[http://www.vmware.com/products/vsphere-hypervisor/overview.html VMware ESXi] ([http://communities.vmware.com/community/vmtn/server/vsphere ESXi5 Forum)]</b><br />
- [[Amahi_in_Xenserver_with_Greyhole|with greyhole]]<br />
- without greyhole</li>
<li>inside <b>[http://www.xenproject.org/downloads/xen-cloud-platform-archives/xen-cloud-platform-16.html XCP] (no longer being developed), [http://xenserver.org/ Xenserver] (opensourced) & [http://www.citrix.com/products/xenserver/overview.html Citrix Xenserver] (Citrix and Opensource versions are the same thing as of 6.2 - ([http://xenproject.org/help/questions-and-answers.html Xenproject Q/A] or [http://forums.citrix.com/category.jspa?categoryID=101 Citrix Forums])</b><br />
- with greyhole<br />
- without greyhole</li>
</ul>
<br />
<h3>Related Amahi Wiki Reference:</h3>
<ul>
<li>[[KVM Virtualization|KVM Virtualization in Linux (with lib-virt, etc)]]</li>
<li>[[KVM|Turning your current server into a KVM-capable host (also with lib-virt, etc)]]</li>
<li>[[Amahi_on_a_VM|Amahi in a VM (short intro)]]</li>
<li>[[VirtualBox|VirtualBox on a Fedora 12 Host]]</li>
<li>[[VMware_Server|Setup VMWare Server on a Fedora 14 host]]</li>
<li>[[PhpVirtualBox|Setup PHPVirtualBox - requires VirtualBox already setup]]</li>
<li><b>[https://forums.amahi.org/viewforum.php?f=41 Amahi Forums - Virtualization Section]</b></li>
</ul>
<br />
<h3>reference outside Amahi..</h3>
* [http://wiki.qemu.org/Qemu-doc.html QEMU Manual]
* [http://www.linux-kvm.org/page/Tuning_KVM Tuning KVM]
* [http://www.linux-kvm.org/page/Main_Page KVM / QEMU Wiki]
<br />
<br />
[[Category:Virtualization]]

Access HDA over SSL

2012-11-30T23:03:07Z

Peter Olson: /* Install mod_ssl for ubuntu*/

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
Here I will discuss accessing your Amahi HDA over SSL. This means that you will go to your home page http://hda and it will automatically convert to https://hda.

= Why is this recommended? =
Currently you access your Amahi HDA control panel unsecured. This means that anyone sniffing your network can get the password to your HDA. If your password is compromised then this means they can log in to possibly modify your shares or even access SSH (if you have it enabled). So I recommend anyone using SSH to at least have SSL access to their Amahi HDA.

[[User:Sag47|Sag47]] 00:38, 15 June 2011 (PDT)

'''NOTE:''' This may interfere with [[Hosting_a_website|Hosting a Website]] tutorial.

= Prerequisites =
I assume you already have Fedora 14 installed with Amahi up and running.

= Instructions =
== Back up apache configurations ==
Before doing anything be sure to back up your apache configurations!
{{Code|<pre><nowiki>(cd /etc/httpd/ && tar -czf apache-backup.tar.gz conf.d/)</nowiki></pre>}}

This way if you accidentally screw something up we can start over.

== Install mod_ssl ==
Fedora:
mod_ssl for Apache2 is required for this functionality. Luckily Fedora makes it easy.
{{Code|<pre><nowiki>yum -y install mod_ssl</nowiki></pre>}}

Ubuntu:
Not needed, should already be installed. If not:
{{Code|<pre><nowiki>sudo a2enmod ssl</nowiki></pre>}}

== Generate your own certificates ==
NOTE: Leaving defaults will not make your server less secure. Make sure that you change "asecretpassword" in the commands below to something else. Otherwise any commands which don't have "asecretpassword" in it can be copied and pasted. This has to do with the challenge password for the private key. If you don't understand what I mean then you should read about [http://en.wikipedia.org/wiki/Public-key_cryptography public-key cryptography] which is essentially what SSL uses.
{{Code|
<pre><nowiki>mkdir /etc/httpd/ssl.crt

openssl genrsa -des3 -passout pass:asecretpassword -out /etc/httpd/ssl.crt/server.key.org 1024

openssl req -new -passin pass:asecretpassword -passout pass:asecretpassword -key /etc/httpd/ssl.crt/server.key.org -out /etc/httpd/ssl.crt/server.csr -days 3650

openssl req -x509 -passin pass:asecretpassword -passout pass:asecretpassword -key /etc/httpd/ssl.crt/server.key.org -in /etc/httpd/ssl.crt/server.csr -out /etc/httpd/ssl.crt/server.crt -days 3650

openssl rsa -passin pass:asecretpassword -in /etc/httpd/ssl.crt/server.key.org -out /etc/httpd/ssl.crt/server.key

mkdir /etc/httpd/ssl.key

mv /etc/httpd/ssl.crt/server.key /etc/httpd/ssl.key/server.key

chmod 400 /etc/httpd/ssl.key/server.key</nowiki></pre>}}

== Modify apache initialization ==
Modify the apache initialization for allowing SSL virtual hosts. Just in case you decide you want more than one virtual host to be capable of SSL.
{{Code|<pre><nowiki>(cd /etc/httpd/conf.d/ && echo 'NameVirtualHost *:443' >> ./00-init.conf)</nowiki></pre>}}

== Create your HDA SSL virtual host ==
Now you need your HDA virtual host over SSL. The default configuration is pretty good so let's use that.
{{Code|<pre><nowiki>cd /etc/httpd/conf.d/
cp 01-platform.conf 01-platform-ssl.conf</nowiki></pre>}}
You need to modify 01-platform-ssl.conf and replace the line with "<VirtualHost *:80>" to the following lines...
{{Text|
<pre><nowiki><VirtualHost *:443>
SSLEngine on
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /etc/httpd/ssl.crt/server.crt
SSLCertificateKeyFile /etc/httpd/ssl.key/server.key</nowiki></pre>
}}
Leave the rest of the file intact as you found it. This way the server utilizes the SSL certificates you created for yourself.

== Create a redirect from HDA to secured HDA ==
Modify /etc/httpd/conf.d/'''01-platform.conf''' and go down to the rewrite rules. Below the last rewrite rule just before the line "# this was only for FCGI" put the following code.
{{Text|
<pre><nowiki>RewriteCond %{HTTPS} !=on
RewriteRule ^(.*) https://%{SERVER_NAME}$1 [R,L]</nowiki></pre>
}}

== Restart the Apache2 server ==
Restart your server to apply the changes you've made. If you did everything right you shouldn't receive any warnings when restarting the server.
{{Code|service httpd restart}}

= Finished =
Now that you're done go ahead and visit http://hda and watch it turn into https://hda! Understand that the certificates you generated have not been verified by a certificate authority so you'll need to confirm a security exception.

= Troubleshooting =

== Apache error ==
If you get an error when you restart Apache (httpd) about a bad configuration then it is probably because you directly copied and pasted from this wiki. When you copy the code then sometimes a null character is also copied which is hidden to most text editors.

A way to solve this is to delete and retype the first an last character of each line which Apache is complaining about. You can then test your configuration again.
{{Code|<pre><nowiki>service httpd configtest</nowiki></pre>}}

If all goes well and you get "Syntax OK" then you can start your Apache server again.
{{Code|<pre><nowiki>service httpd start</nowiki></pre>}}

If all things end badly and you can't figure it out then it is possible to restart this tutorial from scratch. Just start it over.

== How do I start over? ==
Run the following command sequence.
{{Code|
<pre><nowiki>yum -y remove mod_ssl
rm -rf /etc/httpd/ssl.crt
rm -rf /etc/httpd/ssl.key
(cd /etc/httpd/conf.d/ && rm -f *-ssl.conf)
(cd /etc/httpd/ && tar -xzf apache-backup.tar.gz)</nowiki></pre>
}}
Then you can start the instructions again from step one.

= See also =
[[Secure App Access]]<br />
[[Access Joomla over HTTPS]]

Mount Shares Locally

2012-11-20T21:05:52Z

Peter Olson: Adding new shares section

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}

<b>NOTE:</b> Recommend not using copy and paste for the steps below. It often introduces hidden characters which causes failure in the script.

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

== Download and Setup ==

* As '''root:''' Install the mount_shares_locally initd script:
=== On Ubuntu ===
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
sudo apt-get install cifs-utils curl
sudo curl -o /etc/init.d/mount_shares_locally http://dl.amahi.org/mount_shares_locally
sudo chmod +x /etc/init.d/mount_shares_locally
sudo update-rc.d mount_shares_locally defaults
</div>

=== On Fedora ===
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally
</div>

== Configuration ==

* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username. Example '''username="amahi"'''
{{Code|Code= nano /etc/init.d/mount_shares_locally}}
* Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
{{Code|Code= nano /home/YourHDA_username/.smb_credentials}}
*Enter the following:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=your_username
password=your_password
domain=HOME
</div>
'''NOTE:''' your_username and your_password in the .smb_credentials file needs to be the original username and password you created when you installed fedora.

*To test your new mounts, you can execute '''service mount_shares_locally start'''<br/>

'''service mount_shares_locally stop''' will unmount the local shares.<br/>

'''NOTE:''' If you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now (<u>DO NOT</u> remove the drive mount lines). The above initd script replaces all this.

== Re-mount to Add new shares ==
If you added new share to greyhole via the web admin. This does not automatically mount locally. You need to restart your mount script by running '''service mount_shares_locally restart'''. This will unmount and remount all your shares, adding all the new shares you added.

== Where everything is mounted ==
You will find the mounted shares in ''/mnt/samba/*''<br/>
For example, your "Pictures" share would be located at '''/mnt/samba/Pictures'''

== Unable to mount locally after upgrading to Amahi6 ==
If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.

[root@localhost ~]# /etc/init.d/mount_shares_locally start
Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
[ OK ]

It's easily fixed by installing the missing dependency.

{{Code|yum install cifs-utils}}

Now it should work fine to run

{{Code|/etc/init.d/mount_shares_locally start}}

== MySQL Problems With Newer Versions of Greyhole ==

Since Greyhole moved from SQL Lite to MySQL, you may hit a problem where Greyhole and the mount_shares_locally script both attempt to start before MySQL in bootup, leading to the services not starting properly. If this happens, you can try this to fix it:

{{Code|ls /etc/rc.d/rc3.d/}}
* Look for any entries marked S-1. If there are any, they need to be removed. Run the following as root:

{{Code|rm S-1*}}

Mount Shares Locally

2012-11-20T20:52:53Z

Peter Olson: Added headings g/c it looked like the lower section wasn't required for ubuntu since it seemed like it was only under Fedora heading...

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}

<b>NOTE:</b> Recommend not using copy and paste for the steps below. It often introduces hidden characters which causes failure in the script.

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

== Download and Setup ==

* As '''root:''' Install the mount_shares_locally initd script:
=== On Ubuntu ===
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
sudo apt-get install cifs-utils curl
sudo curl -o /etc/init.d/mount_shares_locally http://dl.amahi.org/mount_shares_locally
sudo chmod +x /etc/init.d/mount_shares_locally
sudo update-rc.d mount_shares_locally defaults
</div>

=== On Fedora ===
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally
</div>

== Configuration ==

* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username. Example '''username="amahi"'''
{{Code|Code= nano /etc/init.d/mount_shares_locally}}
* Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
{{Code|Code= nano /home/YourHDA_username/.smb_credentials}}
*Enter the following:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=your_username
password=your_password
domain=HOME
</div>
'''NOTE:''' your_username and your_password in the .smb_credentials file needs to be the original username and password you created when you installed fedora.

*To test your new mounts, you can execute '''service mount_shares_locally start'''<br/>

'''service mount_shares_locally stop''' will unmount the local shares.<br/>

'''NOTE:''' If you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now (<u>DO NOT</u> remove the drive mount lines). The above initd script replaces all this.

== Where everything is mounted ==
You will find the mounted shares in ''/mnt/samba/*''<br/>

== Unable to mount locally after upgrading to Amahi6 ==
If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.

[root@localhost ~]# /etc/init.d/mount_shares_locally start
Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
[ OK ]

It's easily fixed by installing the missing dependency.

{{Code|yum install cifs-utils}}

Now it should work fine to run

{{Code|/etc/init.d/mount_shares_locally start}}

== MySQL Problems With Newer Versions of Greyhole ==

Since Greyhole moved from SQL Lite to MySQL, you may hit a problem where Greyhole and the mount_shares_locally script both attempt to start before MySQL in bootup, leading to the services not starting properly. If this happens, you can try this to fix it:

{{Code|ls /etc/rc.d/rc3.d/}}
* Look for any entries marked S-1. If there are any, they need to be removed. Run the following as root:

{{Code|rm S-1*}}