Had to manually patch it as your system has had a few changes to that file
since what I was working from (911) . I am just doing my backup before
rebuilding.
> Thu May 25 2017 12:38:04 PM EDT from IGnatius T Foobar @ Uncensored
>Subject: Re: Debugging?
>
>Rather than working in a branch
Rather than working in a branch I'm just committing locally on my dev system
and not pushing to master. I made that available at
git://dev.citadel.org/root/citadel
so you can follow it and track the progress of our changes.
But if you just want the debug logs to shut up, the patch is at
I put the changes in the repo on dev.citadel.org where I'm working, not on
the master. I'm not sure how to push just one change. How about a patch?
If you do not want to push more changes to webcit until ng, you can put a
little poke towards ctdlsh for configuring the email addresses at least to
start. However you want to do it. So if I pull the latest from master, I will
have the debug fixed? I cannot keep filling my system with
Ok, that explains it. I replaced the entire logging subsystem because it
was too complex. Every log message now has a prefix so you can filter what
you want to see using grep and other tools. The benefit is that you can read
the logs using tools you already know how to use, and all of the
Yes, it is a problem. :) I thought that the writing to the different log
levels was controlled by the checkboxes in webcit. How can I disable writing
unless it is notice or greater?
> Tue May 23 2017 11:00:24 PM EDT from IGnatius T Foobar @ Uncensored
>Subject: Re: Debugging?
>
>
>>Ig,
>Ig, do you have debug logging enabled in the master by default? I do not
have
>logging on, but am getting my drives filling with log info to syslog, debug
>and daemon.log.
Yes, we write to all log levels all the time. It is expected that if you
need debugging you'll configure your
