FreeBSD support being added to GlusterFS

Harshavardhana harsha at harshavardhana.net
Sun Jul 6 07:12:19 UTC 2014


>
> [2014-07-05 23:32:08.694245] I [MSGID: 100030] [glusterfsd.c:1998:main] 0-glusterd: Started running glusterd version  (args: glusterd --debug)
> [2014-07-05 23:32:08.694289] D [logging.c:1781:__gf_log_inject_timer_event] 0-logging-infra: Starting timer now. Timeout = 120, current buf size = 5
> [2014-07-05 23:32:08.694482] D [MSGID: 0] [glusterfsd.c:614:get_volfp] 0-glusterfsd: loading volume file /usr/local/etc/glusterfs/glusterd.vol
> [2014-07-05 23:32:08.697067] I [glusterd.c:1215:init] 0-management: Using /var/db/glusterd as working directory
> [2014-07-05 23:32:08.697124] C [logging.c:2334:gf_cmd_log_init] 0-management: No such file or directory
> [2014-07-05 23:32:08.697135] C [glusterd.c:1231:init] 0-this->name: Unable to create cmd log file /usr/local/var/log/glusterfs/.cmd_log_history
>

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'

glusterfsd/src/Makefile.am:     $(INSTALL) -d -m 755
$(DESTDIR)$(localstatedir)/log/glusterfs

^^ this should take care of the problematic directory.

Can you check if 'ls -l /usr/local/var/log' exists? as a work-around
you can compile with

# ./configure --localstatedir=/var and it would seem like FreeBSD has /var/log

-- 
Religious confuse piety with mere ritual, the virtuous confuse
regulation with outcomes


More information about the freebsd-fs mailing list