Date: Sun, 6 Jul 2014 11:32:07 -0700 From: Jordan Hubbard <jkh@mail.turbofuzz.com> To: Harshavardhana <harsha@harshavardhana.net> Cc: freebsd-fs@freebsd.org Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <0ABAE2AC-BF1B-4125-ACA9-C6177D013E25@mail.turbofuzz.com> In-Reply-To: <CAAeUqd1m_FxPWCVft5tmeok8QFsEZWGM-5QV20=mq8MeU=7EbA@mail.gmail.com> References: <C647EDA1-EA93-4A66-B59D-3B5F959DC0E0@gluster.org> <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> <0F20AEEC-6244-42BC-815C-1440BBBDE664@mail.turbofuzz.com> <20140629203746.GI34108@ivaldir.etoilebsd.net> <CAAeUqd0=CdwaVjZjUc4PKxD_gxpydVqCy4tebywi=iV3gkpz1Q@mail.gmail.com> <1A58F492-946F-46D4-A19E-2734F368CDAC@mail.turbofuzz.com> <CAAeUqd1m_FxPWCVft5tmeok8QFsEZWGM-5QV20=mq8MeU=7EbA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 6, 2014, at 12:12 AM, Harshavardhana <harsha@harshavardhana.net> = wrote: > Just tested this on FreeBSD 10 after 'rm -rf /usr/local' and complete > GlusterFS recompile/install - glusterd doesn't indicate this issue. A > dummy directory "/usr/local/var/log/glusterfs" directory is created > nevertheless after a 'make install' >=20 > glusterfsd/src/Makefile.am: $(INSTALL) -d -m 755 > $(DESTDIR)$(localstatedir)/log/glusterfs >=20 > ^^ this should take care of the problematic directory. >=20 > Can you check if 'ls -l /usr/local/var/log' exists? as a work-around > you can compile with I can make the /usr/local/var/log/glusterfs directory and it gets much = further. That said, is there some special configure flags we should be = passing in our version of the port to properly stuff glusterfs into /var = instead? Your email tends to imply that we should be passing = =97localstatedir, which we can certainly do no problem, I=92m just = wondering if that=92s your long-term plan. Again, this is our port: = https://github.com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs The fundamental issue with /usr/local is, again, that /usr/local is = read-only on FreeNAS. If there are configuration files that glusterfs = expects to be modifiable, they can=92t live anywhere in /usr/local, nor = of course can any temporary files or log files. We have made special = provisions for /etc and /var such that those can be modified, so we = basically just need to compile gluster as a =93system service=94 and put = it in the system directories (e.g. prefix is /, not /usr/local). Thanks - I think we=92re getting closer! Now that glusterd is actually = running, I just need to figure out how to test it. :) - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0ABAE2AC-BF1B-4125-ACA9-C6177D013E25>