On May 4, 2015 20:17, Niels de Vos wrote:
>
> On Mon, May 04, 2015 at 07:57:23PM +0530, Raghavendra Talur wrote:
> > On Thursday 30 April 2015 02:28 PM, Kaushal M wrote:
> > >The log-level is set by default to
> > >/var/log/etc-glusterfs-glusterd.vol.log, even when running in
> > >`-N` mode.
On Mon, May 04, 2015 at 07:57:23PM +0530, Raghavendra Talur wrote:
> On Thursday 30 April 2015 02:28 PM, Kaushal M wrote:
> >The log-level is set by default to
> >/var/log/etc-glusterfs-glusterd.vol.log, even when running in
> >`-N` mode. Only when running in `--debug` the log itself is redirected
On Thursday 30 April 2015 02:28 PM, Kaushal M wrote:
The log-level is set by default to
/var/log/etc-glusterfs-glusterd.vol.log, even when running in
`-N` mode. Only when running in `--debug` the log itself is redirected
to stdout and stderr.
Redirecting the output as Kaleb suggestes is the easi
The log-level is set by default to
/var/log/etc-glusterfs-glusterd.vol.log, even when running in
`-N` mode. Only when running in `--debug` the log itself is redirected
to stdout and stderr.
Redirecting the output as Kaleb suggestes is the easiest and least
intrusive fix here.
On Thu, Apr 30, 2015
On Thursday 30 April 2015 10:03 AM, Atin Mukherjee wrote:
On 04/30/2015 01:04 AM, Niels de Vos wrote:
On Wed, Apr 29, 2015 at 09:14:37PM +0200, Niels de Vos wrote:
On Wed, Apr 29, 2015 at 12:30:20PM -0400, Kaleb S. KEITHLEY wrote:
Any reason you don't want to run it as: `glusterd --xlator-o
On 04/30/2015 01:04 AM, Niels de Vos wrote:
> On Wed, Apr 29, 2015 at 09:14:37PM +0200, Niels de Vos wrote:
>> On Wed, Apr 29, 2015 at 12:30:20PM -0400, Kaleb S. KEITHLEY wrote:
>>>
>>> Any reason you don't want to run it as: `glusterd --xlator-option
>>> *.upgrade=on -N > /dev/null 2>&1` ?
>>
>>
On Wed, Apr 29, 2015 at 09:14:37PM +0200, Niels de Vos wrote:
> On Wed, Apr 29, 2015 at 12:30:20PM -0400, Kaleb S. KEITHLEY wrote:
> >
> > Any reason you don't want to run it as: `glusterd --xlator-option
> > *.upgrade=on -N > /dev/null 2>&1` ?
>
> I think it would be nicer to use --log-level=/de
On Wed, Apr 29, 2015 at 12:30:20PM -0400, Kaleb S. KEITHLEY wrote:
>
> Any reason you don't want to run it as: `glusterd --xlator-option
> *.upgrade=on -N > /dev/null 2>&1` ?
I think it would be nicer to use --log-level=/dev/null instead, or would
that not override the -N option?
Niels
>
>
>
On Apr 29, 2015 22:00, "Kaleb S. KEITHLEY" wrote:
>
>
> Any reason you don't want to run it as: `glusterd --xlator-option
> *.upgrade=on -N > /dev/null 2>&1` ?
No reason. Just felt it is not really intuitive or explanatory on why someone
should compulsorily use no-daemon option when starting
On Wednesday 29 April 2015 09:26 PM, Kaushal M wrote:
If we were to run without `-N`, in daemon mode, yum wouldn't know when
glusterd actually finished the upgrade process. Yum would consider the
parent process returning to be the end.
I did an experiment and here is what I found,
[root@192 ~]
Any reason you don't want to run it as: `glusterd --xlator-option
*.upgrade=on -N > /dev/null 2>&1` ?
On 04/29/2015 11:56 AM, Kaushal M wrote:
If we were to run without `-N`, in daemon mode, yum wouldn't know when
glusterd actually finished the upgrade process. Yum would consider the
parent
If we were to run without `-N`, in daemon mode, yum wouldn't know when
glusterd actually finished the upgrade process. Yum would consider the
parent process returning to be the end.
On Wed, Apr 29, 2015 at 9:17 PM, Raghavendra Talur wrote:
> Hi,
>
> As part of the yum upgrade procedure, when gl
Hi,
As part of the yum upgrade procedure, when glusterfs-server is updated
we run glusterd in no daemon mode along with upgrade option with this
command.
glusterd --xlator-option *.upgrade=on -N
This helps us update our vol files with new defaults along with
few other things.(say we added a new
13 matches
Mail list logo
