[Gluster-devel] OS X porting merged

[Harshavardhana]

>
>   $ sudo glusterd --debug
>   [2014-05-03 20:49:34.684205] I [MSGID: 100030] [glusterfsd.c:2016:main] 0-glusterd: Started running glusterd version 3.5qa2 (args: glusterd --debug)
>   [2014-05-03 20:49:34.684386] D [MSGID: 0] [glusterfsd.c:614:get_volfp] 0-glusterfsd: loading volume file /Users/jc/local/gluster/etc/glusterfs/glusterd.vol
>   [2014-05-03 20:49:34.685497] I [glusterd.c:1228:init] 0-management: Using /var/lib/glusterd as working directory
>   [2014-05-03 20:49:34.685536] E [common-utils.c:105:mkdir_p] 0-: /var is a symlink
>   [2014-05-03 20:49:34.685549] C [glusterd.c:1154:glusterd_init_snap_folder] 0-management: Unable to create directory /var/run/gluster/snaps ,errno = 17
>   [2014-05-03 20:49:34.685558] C [glusterd.c:1234:init] 0-management: Unable to create snap backend folder
>   $
>
> The "E [common-utils.c:105:mkdir_p] 0-: /var is a symlink" seems a bit weird.
> (Sure it's a symlink, who cares? why is that an error?)  The "Unable to create
> snap backend folder" seems like a bug in code merged since yesterday. :(  I
> don't have time to isolate the exact commit which introduces this just yet.
>
> Anyway, it can be worked around by  "sudo mkdir -p /var/run/gluster/snaps"
> before running glusterd.  Then the sig 11 error from above happens.
>

Even that is fixed here - http://review.gluster.com/#/c/7558/


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