I second Your comments and concerns... I also prefer the prefix approach, but am affraid that it's to late for 1.3. Bogdan, Daniel, Henning and others indeed have a better view of this...
But how about "1.3.1" road-map? I'm saying an intermediary numeration, since 1.4 is, in my understant, to far away from now (more than 4 months, no?) and they are many improvements already pointed and registered as "features requests"... Edson >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:devel- >[EMAIL PROTECTED] On Behalf Of Andreas Heise >Sent: sexta-feira, 23 de novembro de 2007 19:27 >To: Dan Pascu >Cc: [email protected]; Ovidiu Sas >Subject: Re: [OpenSER-Devel] openser error logs > >I've the same problem since the upgrade to 1.3 and migration to LM_*, >why not add the level as string at begin >of the message like on stdout function? If needed we could add a new >parameter to decide the behavior and >make all admins happy ;-) > >regards, >Andreas > > >Dan Pascu schrieb: >> This is worse than before. I don't want to split my syslog into 4 files >> just to know which ones are errors, which ones are warnings and which are >> notices or info messages. I want to read a single syslog and see if >> something is an error or a warning. I want to see all the messages >> interleaved in their chronological order and to know what is each, not to >> run tail -f on 4 files and restore their order them in my head... >> >> On Friday 23 November 2007, Bogdan-Andrei Iancu wrote: >> >>> Yes :). >>> >>> Regards, >>> Bogdan >>> >>> Ovidiu Sas wrote: >>> >>>> I see. This is done on purpose (new approach). OK. >>>> >>>> Thank you, >>>> Ovidiu >>>> >>>> On Nov 23, 2007 8:18 AM, Bogdan-Andrei Iancu <[EMAIL PROTECTED]> >>>> >> wrote: >> >>>>> oh.....I see....in syslog. >>>>> >>>>> The LM_* functions do not write (in the message) the logging level >>>>> when using syslog - this is directly passed to syslog, so you can >>>>> use syslog to divert the errors in a different log file. >>>>> >>>>> Regards, >>>>> Bogdan >>>>> >>>>> Ovidiu Sas wrote: >>>>> >>>>>> Hmmm ... I doesn't. >>>>>> >>>>>> The following LM_ERR: >>>>>> parse_from.c: LM_ERR("bad from header\n"); >>>>>> will generate the following syslog: >>>>>> Nov 23 08:54:57 localhost /usr/local/sbin/openser[22588]: >>>>>> core:parse_from_header: bad from header >>>>>> >>>>>> >>>>>> Regards, >>>>>> Ovidiu Sas >>>>>> >>>>>> On Nov 23, 2007 3:35 AM, Bogdan-Andrei Iancu >>>>>> >> <[EMAIL PROTECTED]> wrote: >> >>>>>>> Hi Ovidiu, >>>>>>> >>>>>>> But if you use LM_ERR(), it will always prefix the ERROR string. >>>>>>> Isn't this was you want? >>>>>>> >>>>>>> regards, >>>>>>> bogdan >>>>>>> >>>>>>> Ovidiu Sas wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> >>>>>>>> I suggest to prefix all the openser error logs with the prefix >>>>>>>> "ERR:". This will make debugging more easier. >>>>>>>> Today, all the logs are having the same format and it is not >>>>>>>> straight forward to spot an error in the logs. >>>>>>>> This should be fairly easy with the new LM_ logging format. >>>>>>>> >>>>>>>> >>>>>>>> Regards, >>>>>>>> Ovidiu Sas >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Devel mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.openser.org/cgi-bin/mailman/listinfo/devel >>>>>>>> >>> _______________________________________________ >>> Devel mailing list >>> [email protected] >>> http://lists.openser.org/cgi-bin/mailman/listinfo/devel >>> >> >> >> >> > > >_______________________________________________ >Devel mailing list >[email protected] >http://lists.openser.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/devel
