If this doesn't work for you, it should be straightforward to revert to Netatalk 2.1.5, assuming you followed the backup instructions. It resumed using existing sparsebundle backups. I have tested this afpd binary with both Snow Leopard 10.6.8 and Lion 10.7. You must still connect to the share you want to use for Time Machine before you can select it in the Time Machine system preferences in Lion. Nas# /usr/local/etc/rc.d/avahi-daemon startĪFP shares should mount as normal. Nas# cp /etc/local/avahi/services/rvice /conf/base/etc/local/avahi/services/ The following will make this change permanent after reboot avahi-services/rvice /etc/local/avahi/services This is necessary since this afpd binary is not avahi aware. Replace the bits with curly brackets with your installation information. ![]() uams /usr/local/libexec/netatalk-uamsĬreate a new directory for the signature fileĮdit the rvice file in avahi-services. Nas# mv /usr/local/libexec/netatalk-uams /usr/local/libexec/netatalk-uams-2.1.5Ĭd to the netatalk-2.2 directory that was untarred. Nas# mv /usr/local/sbin/papd /usr/local/sbin/papd-2.1.5 Nas# mv /usr/local/sbin/cnid_dbd /usr/local/sbin/cnid_dbd-2.1.5 Nas# mv /usr/local/sbin/cnid_metad /usr/local/sbin/cnid_metad-2.1.5 Nas# mv /usr/local/sbin/atalkd /usr/local/sbin/atalkd-2.1.5 Nas# mv /usr/local/sbin/afpd /usr/local/sbin/afpd-2.1.5 Untar and you will find the following files: Scp netatalk-2.2.tar.gz to your FreeNAS installation. In order to make your changes survive a reboot you must mount the filesystem read/write: Nas# /usr/local/etc/rc.d/avahi-daemon stop There is an additional file you will need to edit for Avahi and copy into place. ![]() So this afpd binary will not automatically register with Avahi. I could not get the configure script to recognize Avahi on my FreeBSD 8.2 build box. I have compiled Netatalk 2.2 from Frank Lahm's master tag after he merged knu's fixes for FreeBSD. UPDATE 4: How to integrate the contents of the afp_nf file with the rvice file. UPDATE 3: Tarball for amd64 now available. UPDATE 2: Initial release is for x86 systems. UPDATE: Updated tar ball link below with other binaries included, atalkd, cnid_dbd, chid_metad, papd. If someone is interested in doing this for FreeNAS 7 they can pull a snapshot of Frank Lahm's master branch from Sourceforge git and try themselves. These will not work on FreeNAS 7 and I have no plans to try to compile there. There is no warranty or support for the below. I'm currently doing so from a non-standard/supported approach but would like to be able to set my own options on the home share in nf and the FreeNAS UI doesn't seem to provide a way to do this.NOTE: This should only be attempted by those who are comfortable mucking about with their FreeNAS installation. I attempted to modify the /conf/base/etc/local/nf & /conf/base/etc/local/ files hoping that was where the middleware was starting off but that doesn't seem to do the trick.ĮDIT/TLDR: I guess the gist of what I'm interested in is if anyone knows how to customize the home share. but I was wondering if anyone else has either come across this issue or come across a similar issue and knows of a way to "fix" FreeNAS so manual changes to configuration files will persist. I'm considering writing a script to watch the file, update it when necessary & HUP afpd. The problem is, anytime the AFP service is restarted the middleware wipes out my custom change which results in the home shares no longer being valid Time Machine destinations. I couldn't find a way to achieve this setup with the FreeNAS Web UI, but I was able to manually modify /etc/local/nf to add 1 line to the section that does the job:Īdding that last line and HUP'ing the afpd process does the trick. The above basically translates to each user has access to their home directory which is shared via netatalk/afpd and enables TM Lock Stealing which is required for Mac clients to be able to use the resulting shares for Time Machine. ~/ "home" cnidscheme:dbd options:usedots,upriv,tm,noadouble ea:ad Neither of this will work in my environment, so I'm trying to achieve the same setup I have on my old Debian Linux server running netatalk/afpd that is currently handling backups with this configuration: All the forum threads that I've read have people either creating separate zfs targets for each user/client or creating 1 share and granting all users access to see it. ![]() ![]() I've been trying to setup a FreeNAS 11 system to serve as a Time Machine server for multiple users/clients.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |