The RPM install does a `checkcfg --add ...`; they will start after a reboot without any additional steps on your part. The only thing you need to do after an install is `service glusterd start`. ----- Original Message ----- From: "Lonni J Friedman" <netllama at gmail.com> To: "Kaleb Keithley" <kkeithle at redhat.com> Cc: gluster-users at gluster.org Sent: Tuesday, September 18, 2012 2:31:54 PM Subject: Re: glusterd vs. glusterfsd On Tue, Sep 18, 2012 at 11:30 AM, Kaleb Keithley <kkeithle at redhat.com> wrote: > > If you mean you're using RPMs from my fedorapeople.org repo, those are not official. I put them there to be helpful, that's about it. yes, those. thanks for maintaining them, they are great! > > With those RPMs you need both init scripts, but as a an admin you should only ever use the glusterd script. so i should only set glusterd to run at boot, and ignore glusterfsd altogether ? > > > > ----- Original Message ----- > From: "Lonni J Friedman" <netllama at gmail.com> > To: gluster-users at gluster.org > Sent: Tuesday, September 18, 2012 2:06:29 PM > Subject: glusterd vs. glusterfsd > > I'm running version 3.3.0 on Fedora16-x86_64. The official(?) RPMs > ship two init scripts, glusterd and glusterfsd. I've googled a bit, > and I can't figure out what the purpose is for each of them. I know > that I need one of them, but I can't tell which for sure. There's no > man page for either, and running them with --help returns the same > exact output. Do they have separate purposes? Do I only need one or > both running on the bricks? > > thanks > __________________________________________
