= General Linux/HDA Commands =
Fedora (root user)
<table border="1">
<tr>
</tr>
<tr>
<td>systemctl restart httpd.service httpd start</td>
<td>restart web server</td>
</tr>
<tr>
<td>yum dnf -y update</td><td>automatically update fedoraFedora</td>
</tr>
<tr>
<td>rpm -Uvh http:q hda-platform</td><td>check to see what version of HDA you're running</dl.getdropbox.comtd></utr></364883table><br /Amahi>Ubuntu (precede with sudo)<table border="1"><tr><th>Command</th><th>Action</th></hda-platform-*.*-*.noarch.rpmtr><tr><td>service apache2 restart</td><td>updates HDArestart web server</td>
</tr>
<tr>
<td>rpm apt-q hdaget -platformy upgrade</td><td>check to see what version of HDA you're runningautomatically update Ubuntu</td>
</tr>
</table><br />
= HDA Script Commands =
'''NOTE:''' Must be run from the '''''/var/hda/platform/html/script''''' directory.
<table border="1">
<tr>
</table>
'''NOTE:''' Must be run from the '''''/var/hda/platform/html/script''''' directory.
'''NOTE:''' Can be run from anywhere (located in '''/usr/bin''').
<table border="1">
</tr>
<tr>
<td>[[Application_Install_Scripts#hda-create-db-and-userutility script|hda-create-db-and-user]]</td><td>create MySql MariaDB user and database</td>
</tr>
<tr>
<td>hda-new-install</td>
<td>manual install for AmahiDEPRECATED</td>
</tr>
<tr>
<td>refresh HDA shares</td>
</tr>
<tr>
<td>hda-alias</td>
<td>SYSTEM USE ONLY</td>
</tr>
<tr><td>hda-fix-sudoers</td>
<td>SYSTEM USE ONLY</td>
</tr>
<tr><td>hda-install</td>
<td>Amahi 7 or greater ONLY</tr>
<tr><td>hda-install-file</td>
<td>SYSTEM USE ONLY</td>
</tr>
<tr><td>hda-register-apps</td>
<td>SYSTEM USE ONLY</td>
</tr>
<tr><td>hda-settings</td>
<td>Dumps current settings</tr>
<tr><td>hda-update-webapps</td>
<td>SYSTEM USE ONLY</td>
<tr><td>hda-add-apache-sudoers</td>
<td>SYSTEM USE ONLY</td>
</tr>
<tr><td>hda-diskmount</td>
<td>Used to mount disk drives</td>
</tr>
<tr><td>hda-gems-install</td>
<td>SYSTEM USE ONLY</td>
</tr>
</table>
'''NOTE:''' Can be run from anywhere (located in '''/usr/bin''').
= Miscellaneous =
<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>Clear DNS cache on HDA</td>
</tr>
<tr><td>[[Application_Install_Scripts#The amahi-download utility script|amahi-download]]</td><td>similar to wget, but uses SHA1</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.
-C, --cancel-fsck Cancel all scheduled fsck.
-l, --balance Balance available space on storage pool drives.
-s, --stats Display storage pool statistics.
-i, --iostat I/O statistices for your storage pool drives.
-L, --logs Display new greyhole.log entries as they are logged.
-S, --status Display what the Greyhole daemon is currently doing.
-q, --view-queue Display the current work queue.
-a, --empty-trash Empty the trash.
-b, --debug=filename Debug past file operations.
-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.
-r, --replace[=path] Tell Greyhole that you replaced the drive at <path>.
-X, --fix-symlinks Try to find a good file copy to point to for all broken
symlinks found on your shares.
-p, --delete-metadata<=path>
Delete all metadata files for <path>, which should be a
share name, followed by the path to a file that is gone
from your storage pool.
-U, --remove-share<=share_name>
Move the files currently inside the specified share from the
storage pool into the shared folder (landing zone),
effectively removing the share from Greyhole's storage pool.
For --stats and --view-queue, the available OPTIONS are:
-j, --json Output the result as JSON, instead of human-readable text.
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-metadata-store
Speed up fsck by skipping the scan of the metadata store
directories. Scanning the metadata stores 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 or smb.conf paths 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, a
sub-directory of a Samba share, or any directory on a
storage pool drive.
-o, --find-orphaned-files
Scan for files with no metadata in the storage pool drives.
This will allow you to include existing files on a drive
in your storage pool without having to copy them manually.
-k, --checksums Read ALL files in your storage pool, and check that
file copies are identical. This will identify any problem
you might have with your file-systems.
NOTE: this can take a LONG time to complete, since it will read
everything from all your drives!
-m, --delete-orphaned-metadata
When fsck find metadata files with no file copies, delete those
metadata files. If the file copies re-appear later, you'll need
to run fsck with --find-orphaned-files to have them reappear in
your shares.
