Hello.
I compiled dbmail rev 1940.
Run dbmail-imapd and no messages at all.(TRACE_LEVEL=5)
no forking, no work.
I attach output from "strace dbmail-imapd -n -v" command
(only "dbmail-imapd -V" and "dbmail-imapd -h" give me output)
--
Oleg Lapshin
- attach --
$ s
Add:
TRACE_SYSLOG=1
TRACE_STDERR=0
to your dbmail.conf as documented in the example config.
This one had me stumped as well last week :-(
Oleg Lapshin wrote:
> Hello.
> I compiled dbmail rev 1940.
> Run dbmail-imapd and no messages at all.(TRACE_LEVEL=5)
> no forking, no work.
>
> I at
That's dumb, why are those TRACE_FATAL when not found? I just copied it
twice more to the new options; I don't think any failure to find the
TRACE_* config options should be FATAL, just result in sane defaults.
I'll make it part of my trace-fixing project to fix that!
Aaron
On Fri, 2005-12-16 at
В сообщении от 16 декабря 2005 13:44 Paul J Stevens написал(a):
> Add:
>
> TRACE_SYSLOG=1
> TRACE_STDERR=0
>
> to your dbmail.conf as documented in the example config.
>
> This one had me stumped as well last week :-(
Sorry ;)
Output:
Dec 16 13:48:23 bagira dbmail/imap4d[3862]: dbmysql.c,db_conne
On Fri, 2005-12-16 at 14:05 +0300, Oleg Lapshin wrote:
> В сообщении от 16 декабря 2005 13:44 Paul J Stevens написал(a):
> > Add:
> >
> > TRACE_SYSLOG=1
> > TRACE_STDERR=0
> >
> > to your dbmail.conf as documented in the example config.
> >
> > This one had me stumped as well last week :-(
>
> Sor
> The problem was that you didn't have the two config items TRACE_SYSLOG
> and TRACE_STDERR. I thoughlessly made those mandatory with a stupid
> fatal error message.
NO!
When I try to run dbmail-imapd with this in config:
TRACE_LEVEL=5
TRACE_SYSLOG=1
TRACE_STDERR=0
host=localhost # host for
On Thu, 2005-12-15 at 14:24 -0800, Kevin Brown wrote:
> Geo Carncross wrote:
> > I know we talked about this earlier, but I think for 2.2 we need to make
> > it possible to have multiple queries- we talked about it per database
> > layer, but why not a global conformance level setting?
> >
> > DB_
On Thu, 2005-12-15 at 14:16 -0800, Kevin Brown wrote:
> Paul J Stevens wrote:
> > And I suspect 5.0 will be become a requirement for 2.3+ so we can
> > start working with views, triggers, etc...
>
> Hmm...that would imply ditching SQLite, wouldn't it?
>
> Not that I have a problem with that, mind
There're not fatal. But when they are missing there's no logging at all!
Which effectively hides the cause of any fatal errors :-)
Aaron Stone wrote:
> That's dumb, why are those TRACE_FATAL when not found? I just copied it
> twice more to the new options; I don't think any failure to find the
> T
Wait, but:
if (config_get_value("trace_level", service_name, trace_level) < 0)
trace(TRACE_FATAL, "%s,%s: error getting config!",
__FILE__, __func__);
Oh, cute:
/* FIXME: Always returns 0, which is dandy for debugging. */
int config_get_value(const field_t field_
Geo Carncross wrote:
> On Thu, 2005-12-15 at 14:16 -0800, Kevin Brown wrote:
> > Paul J Stevens wrote:
> > > And I suspect 5.0 will be become a requirement for 2.3+ so we can
> > > start working with views, triggers, etc...
> >
> > Hmm...that would imply ditching SQLite, wouldn't it?
> >
> > Not
On Fri, 2005-12-16 at 11:11 -0800, Kevin Brown wrote:
> Geo Carncross wrote:
> > On Thu, 2005-12-15 at 14:16 -0800, Kevin Brown wrote:
> > > Paul J Stevens wrote:
> > > > And I suspect 5.0 will be become a requirement for 2.3+ so we can
> > > > start working with views, triggers, etc...
> > >
> >
12 matches
Mail list logo
