On Tue, Jul 30, 2013 at 11:39 PM, Balamurugan Arumugam
wrote:
>
>
> - Original Message -
> > From: "Joe Julian"
> > To: "Pablo" , "Balamurugan Arumugam" <
> b...@gluster.com>
> > Cc: gluster-us...@gluster.org, gluster-devel@nongnu.org
> > Sent: Tuesday, July 30, 2013 9:26:55 PM
> > Subjec
- Original Message -
> From: "Joe Julian"
> To: "Pablo" , "Balamurugan Arumugam"
> Cc: gluster-us...@gluster.org, gluster-devel@nongnu.org
> Sent: Tuesday, July 30, 2013 9:26:55 PM
> Subject: Re: [Gluster-users] new glusterfs logging framework
>
> Configuration files should be under /e
- Original Message -
> From: "Joe Julian"
> To: "Pablo" , "Balamurugan Arumugam"
> Cc: gluster-us...@gluster.org, gluster-devel@nongnu.org
> Sent: Tuesday, July 30, 2013 9:26:55 PM
> Subject: Re: [Gluster-users] new glusterfs logging framework
>
> Configuration files should be under /e
The docs (markdown version) are in doc/admin-guide/en-US/markdown for
release-3.4 and master. I'd like to have these converted for 3.3 as well.
I started to automate the publication of the existing content but I
noticed some deficiencies in order to make it happen. I need a title
page that lin
On Tue, Jul 30, 2013 at 7:47 AM, Roberto De Ioris wrote:
>
> > On Mon, Jul 29, 2013 at 10:55 PM, Anand Avati
> > wrote:
> >
> >
> > I am assuming the module in question is this -
> > https://github.com/unbit/uwsgi/blob/master/plugins/glusterfs/glusterfs.c
> .
> > I
> > see that you are not using
On 07/31/2013 12:36 AM, Kaushal M wrote:
> Manual Pages:
>
> To be cleaned up and brought up to date.
>
Can we also try to move the man pages to markdown as well? I tried to
update them for the 3.3 release, but wasn't able to get much done
because the markup language used is hard to make sens
Maybe I should read the whole page instead of just the bullet points
On 07/30/2013 07:52 AM, Vijay Bellur wrote:
On 07/30/2013 06:56 PM, Lubomir Rintel wrote:
Hello everyone,
I've found GlusterFS documentation hard to follow. I've often found
resources useful to me only by accident, scatte
We have to learn from XFS documentation -
http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/index.html
I generally would keep the wiki but extensively support pandoc - which is
quite precise and useful for distribution.
On Tue, Jul 30, 2013 at 12:12 PM, Joe Julian wrote:
> Need
By the way, pandoc does support asciidoc according to
http://johnmacfarlane.net/pandoc/
On 07/30/2013 07:52 AM, Vijay Bellur wrote:
On 07/30/2013 06:56 PM, Lubomir Rintel wrote:
Hello everyone,
I've found GlusterFS documentation hard to follow. I've often found
resources useful to me only by
s/rfc3164/ISO8601/
That's what I get for trying to search from my phone while writing an
email on the train.
On 07/30/2013 08:56 AM, Joe Julian wrote:
Configuration files should be under /etc per FSH standards. Move the
logger.conf to /etc/glusterfs.
I, personally, like json logs since I'm
Need to evolve a process to roll down the latest admin guide on to
gluster.org
I can take care of doing that from the git tree by branch. That should
be fairly easy to automate.
___
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.no
On 30-Jul-2013 8:23 PM, "Vijay Bellur" wrote:
>
> On 07/30/2013 06:56 PM, Lubomir Rintel wrote:
>>
>> Hello everyone,
>>
>> I've found GlusterFS documentation hard to follow. I've often found
>> resources useful to me only by accident, scattered across the wiki, in
>> source tree, blogs or present
On Mon, Jul 29, 2013 at 09:56:09AM -0700, Joe Julian wrote:
> I disagree. Since the cli will not build a volume with it, it doesn't
> need to be in a package. Since its value is purely academic, only the
> source code matters, and it will still be in the git repo and the src
> tarball.
Thats w
Configuration files should be under /etc per FSH standards. Move the
logger.conf to /etc/glusterfs.
I, personally, like json logs since I'm shipping to logstash. :-) My one
suggestion would be to ensure the timestamps are in rfc3164.
Yes, those are complex steps, but the rpm/deb packaging shoul
I think that adding all that 'rsyslog' configuration only to see logs is
too much. (I admit it, I don't know how to configure rsyslog at that
level so that may influence my opinion)
Regards,
El 30/07/2013 06:29 a.m., Balamurugan Arumugam escribió:
Hi All,
Recently new logging framework was
On 07/30/2013 06:56 PM, Lubomir Rintel wrote:
Hello everyone,
I've found GlusterFS documentation hard to follow. I've often found
resources useful to me only by accident, scattered across the wiki, in
source tree, blogs or presentation slides. Lots of documents were on
the other hand inaccurate
> On Mon, Jul 29, 2013 at 10:55 PM, Anand Avati
> wrote:
>
>
> I am assuming the module in question is this -
> https://github.com/unbit/uwsgi/blob/master/plugins/glusterfs/glusterfs.c.
> I
> see that you are not using the async variants of any of the glfs calls so
> far. I also believe you would
Hello everyone,
I've found GlusterFS documentation hard to follow. I've often found
resources useful to me only by accident, scattered across the wiki, in
source tree, blogs or presentation slides. Lots of documents were on
the other hand inaccurate or incomplete, maybe just because GlusterFS
deve
On Sun, Jul 28, 2013 at 11:32 PM, Bryan Whitehead wrote:
> Weekend activities kept me away from watching this thread, wanted to
> add in more of my 2 cents... :)
>
> Major releases would be great to happen more often - but keeping
> current releases "more current" is really what I was talking abou
Hi All,
Recently new logging framework was introduced [1][2][3] in glusterfs master
branch. You could read more about this on doc/logging.txt. In brief, current
log target is moved to syslog and user has an option to this new logging at
compile time (passing '--disable-syslog' to ./configure
On Mon, Jul 29, 2013 at 2:17 PM, Joe Julian wrote:
> As one of the guys supporting this software, I agree that I would like
> bugfix releases to happen more. Critical and security bugs should trigger
> an immediate test release. Other bug fixes should go out on a reasonable
> schedule (monthly?).
21 matches
Mail list logo
