Question for the greyhole ppl!
I just rebuilt an Amahi server and didn't mount a /var/hda/files explicitly.
Instead I just mounted 2 drives as such...
/var/hda/files/drives/hdd01
/var/hda/files/drives/hdd02
.. so where do my files go at copy to shares time?
How does GH deal with this?
no LZ, just drives
no LZ, just drives
SgtFoo
HDA: VM inside oVirt FX-8300 95w (2 cores for HDA), 32GB RAM (2GB for HDA)
My PC: FX-8300, 16GB RAM, 3x 1TB HDDs, Radeon HD6970 2GB video; Win10 Pro x64
Other: PC, Asus 1215n (LXLE), Debian openZFS server (3x(2x2tb) mirrors)
Modem&Network: Thomson DCM475; Asus RT-AC66U; HP 1800-24G switch
HDA: VM inside oVirt FX-8300 95w (2 cores for HDA), 32GB RAM (2GB for HDA)
My PC: FX-8300, 16GB RAM, 3x 1TB HDDs, Radeon HD6970 2GB video; Win10 Pro x64
Other: PC, Asus 1215n (LXLE), Debian openZFS server (3x(2x2tb) mirrors)
Modem&Network: Thomson DCM475; Asus RT-AC66U; HP 1800-24G switch
Re: no LZ, just drives
A Share Landing Zone is the path of that share, as defined in smb.conf (the Samba configuration file). (On Amahi, this is the Location field in the Setup > Shares page).
Example share definition:
[share_name]
path = /path/to/share_name
create mask = 0770
directory mask = 0770
read only = no
available = yes
browseable = yes
writable = yes
guest ok = no
printable = no
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole
Example share definition:
[share_name]
path = /path/to/share_name
create mask = 0770
directory mask = 0770
read only = no
available = yes
browseable = yes
writable = yes
guest ok = no
printable = no
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole
Re: no LZ, just drives
You did not mount a drive to /var/hda/files, but it still exists unless you removed it. On install, that location will be put on the OS drive by default. So all your shares will exist there.
If you removed it, there is a chance you could break Amahi. Some apps write shares specifically to /var/hda/files.
If you removed it, there is a chance you could break Amahi. Some apps write shares specifically to /var/hda/files.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: no LZ, just drives
Hi
Juergen
you mean, the path is hard coded in the app?If you removed it, there is a chance you could break Amahi. Some apps write shares specifically to /var/hda/files.
Juergen
Re: no LZ, just drives
Yes. The app install script for some web apps creates a share. If the /var/hda/files location does not exist, it will not know where to put the share. It may create it on its own, but I would presume it would be on the OS drive.
There has to be a /var/hda/files location for Amahi to work correctly. Now given the drives are mounted in /var/hda/files/drives, that shows the path would exist on the OS drive. The default shares will most likely be located there as well.
There has to be a /var/hda/files location for Amahi to work correctly. Now given the drives are mounted in /var/hda/files/drives, that shows the path would exist on the OS drive. The default shares will most likely be located there as well.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Who is online
Users browsing this forum: No registered users and 18 guests