log4plsql-all-info Mailing List for LOG4PLSQL (Page 6)
Brought to you by:
gmoulard
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(4) |
Jun
(11) |
Jul
(13) |
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(9) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(3) |
Feb
(1) |
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
(5) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
(6) |
2004 |
Jan
(7) |
Feb
(26) |
Mar
(8) |
Apr
(1) |
May
(5) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(4) |
Dec
(8) |
2005 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
(10) |
Jun
(2) |
Jul
|
Aug
(5) |
Sep
|
Oct
(7) |
Nov
|
Dec
|
2006 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(5) |
Sep
(2) |
Oct
(3) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2009 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <log...@li...> - 2004-02-02 17:00:52
|
Guillaume, As I tried to explain to you in our last private email exchange, I think it= =20 is best if we waited for a few months before having this vote. Before=20 joining the ASF, we need to make sure that log4plsql functions as an open=20 project and has at least a CVS repository. The CVS repository was created=20 barely a few days ago. We still need more time to let log4jplsql evolve as= =20 an open source project before making a decision. If other logging PMC members feel that the above arbitrary, then I will=20 gladly abide by the will of the majority. Thank you for your understanding, At 04:11 PM 1/29/2004 +0100, gmo...@us... wrote: >Hi, > >I represent the log4plsql project. > >we would be very happy if PMC accepte to start the >log4plsql incubation process. >We have sent the CLA and the software grant for >log4plsql project. >We have can use the Apache Software License. > >I ask the PMC to be granted committer access and, >consequently, to start >the log4plsql incubation process. > > >Regards, >Guillaume Moulard >gmo...@us... --=20 Ceki G=FClc=FC For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp =20 |
From: <log...@li...> - 2004-01-31 04:14:08
|
I represent the log4plsql project. we would be very happy if PMC accepte to start the log4plsql incubation process. We have sent the CLA and the software grant for log4plsql project. We have can use the Apache Software License. I ask the PMC to be granted committer access and, consequently, to start the log4plsql incubation process. Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ |
From: <log...@li...> - 2004-01-27 22:06:26
|
Hi all, I consider to use Log4plsql (V2.1.1) in a project where a lot of the = code is written in Java, and there is also a lot of PLSQL. I need to = send the logs to certain log files, and it is required that logs from = PLSQL code is same format as logs from Java. Looking at the Log4plsql code, I believe I can benefit from using the = background processing. However, there are some challenges ;-) First I need to dispatch the logs to the correct log file. This should = be possible by using the section functionality to identify log file = destination. Basically each PLSQL package will log to a certain log = file, and pushing the package name as section, it should be fairly easy = to configure the hierarchy in Log4J to dispatch logs to the correct = file. The second challenge is worse. We are a number of developers who each = use our own unix-user and database scheme (user) to run the application. = When logging from one database scheme, the developer expects the logs to = appear in the log files belonging to the corresponding unix user e.g. = located in $HOME/myapp/logs. The Log4plsql package writes logs to pipe = and the background Java logging process receives the logs from this = pipe. But the pipe name is a constant (LOG_PIPE), which means I can only = have one background logging process and it must have write permissions = to all the log directories. I could create a superuser for this purpose = and allow this superuser to write to the developers home directories (or = at least their log directories). The background logging process should = then be run by the superuser. Still it requires the developers to be = able to control logging for their database scheme, which means they must = have write access to the background logging configuration. This is a = little cumbersome. I believe a better approach is to allow the PLSQL logging to control = which pipe to log to. Then I would use one pipe for each database scheme = (say LOG_PIPE_<dbscheme>) and the developer should start a background = logging process from their unix-user and make it log to their logging = directory. Control of the log pipe should be put into the log context = (PLOG.LOG_CTX) and set in the init function. Default could be LOG_PIPE = for backward compatibility. The background Java logging process should = read pipe to use from configuration, the same way it configures db = username/password. Again it could default to LOG_PIPE. I hope you will consider this enhancement. It should be a fairly simple = change to implement - if needed I can send the updates to V2.1.1, but at = the moment I do not have access to compile SQLJ. I realize there are some initiatives to have the Log4plsql project join = the Apache Logging Services project, and I am uncertain to what this = means to the current implementation and future development. Please = advise if you can. BR. Allan |
From: <log...@li...> - 2004-01-22 13:10:52
|
Hi,=20 =20 In my dreams most fantastic, I think to log4db.=20 All database developpeurs can log in table with or without=20 specific database code and after all log is process and=20 send to log4J.=20 Perhaps is insteresting for log4plsql if a test and=20 setup the Chainsaw's JDBCReceiver with log4plsql? Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 =20 -----Message d'origine----- De : Scott Deboy [mailto:sd...@co...] Envoye : mardi 20 janvier 2004 23:11 A : gmo...@us... Objet : log4plsql Hi Guillaume, Not sure if you knew this, but I wanted to let you know there is a JDBCReceiver that can retrieve events from the TLOG table and display them in Chainsaw v2. If you're interested in trying it out or have questions, let me know. Chainsaw v2's page is here: http://logging.apache.org/log4j/docs/chainsaw.html and JDBCReceiver is here: http://cvs.apache.org/viewcvs.cgi/jakarta-log4j-sandbox/src/java/org/apa che/log4j/jdbc/JDBCReceiver.java?rev=3D1.13&view=3Dauto Take care, Scott |
From: <log...@li...> - 2004-01-20 20:02:07
|
Hi, We have a good news for log4plsql project. I wrote a acticle for Oracle Technology Network this autumn and now you can read it in this place: http://otn.oracle.com/pub/articles/moulard_log4plsql.html Thanck to Oracle for this encouraging Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ |
From: <log...@li...> - 2004-01-19 18:02:20
|
Hi,=20 =20 We will put in production status the file=20 http://prdownloads.sourceforge.net/log4plsql/Log4plsql31b.zip =20 in end of January Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoye : lundi 19 janvier 2004 14:41 A : Log...@li... Objet : [log4plsql] log4plsql Please add me to the mailing list. Has the latest release been made yet (scheduled for January 2004) ? This message (including any attachments) is confidential and may be = privileged. If you have received it by mistake please notify the sender = by return e-mail and delete this message from your system. Any = unauthorised use or dissemination of this message in whole or in part is = strictly prohibited. Please note that e-mails are susceptible to change. = Close Premium Finance shall not be liable for the improper or incomplete = transmission of the information contained in this communication nor for = any delay in its receipt or damage to your system. Close Premium Finance = does not guarantee that the integrity of this communication has been = maintained nor that this communication is free of viruses, interceptions = or interference. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
From: <log...@li...> - 2004-01-19 13:41:15
|
Please add me to the mailing list. Has the latest release been made yet (scheduled for January 2004) ? This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. |
From: <log...@li...> - 2003-12-23 16:58:23
|
Hi, The new beta version is enable for test : new in log4plsql -> 3.1 Capability to create a custom log level. new in log4plsql -> 3.0 News features · Log in alert.log, trace file (thank to andreAs for information) · Log with DBMS_OUTPUT (Wait -> SET SERVEROUTPUT ON) . Log full_call_stack · getLOG4PLSQVersion return string Version · getLevelInText return the text level for one level I read a very interesting article write by Steven Feuerstein in Oracle Magazine "Handling Exceptional Behavior" this 2 new features is inspired direcly by this article · assert procedure · default message for each log procedure is now SQLCODE and SQLERRM Update · Update default value of PLOGPARAM.DEFAULT_LEVEL -> DEBUG · Now is possible to log in table and in log4j · ctx and init funtion parameter. · Create of PLOGPARAM for updatable parameter Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ --------------------------------- Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail |
From: <log...@li...> - 2003-12-23 15:59:26
|
Hi, log4plsql want joint this initiative. I have just filled the 2 forms. Which are the following stages? Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ Ceki Gülcü <ce...@qo...> wrote: To begin with, I'd like to inform you that this list is archived at: http://nagoya.apache.org/eyebrowse/SummarizeList?listId=199 The exact incubation process is still the subject of internal debate at the ASF. So I am unable to present you at this time with an ironclad procedure. However, regardless the of exact name of such an such mailing list or the precise web-address where the incubation will occur, we need to have the developers of the software to publicly and formally express their consent to donating their code to the ASF. First the individual(s) or corporation(s) holding the copyright must be identified and listed somewhere. Those individual(s) or corporation(s) should sign a Software grant. See http://apache.org/licenses/software-grant.txt. Second, the individual(s) wishing to continue to work on their software within the ASF must a sign a CLA. See http://apache.org/licenses/cla.txt or http://apache.org/licenses/cla.pdf. There is also a CLA for corporations http://apache.org/licenses/cla-corporate.txt. Please let us know if any of the above is unclear or if you need help with the paperwork. -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp --------------------------------- Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail |
From: <log...@li...> - 2003-12-23 11:37:38
|
FUNCTION islevelEnabled -- fonction outil appeler par les is[Debug|Info|Warn|Error]Enabled ( pCTX IN LOG_CTX, -- Context pLEVEL IN TLOG.LLEVEL%TYPE -- Level a tester ) RETURN BOOLEAN IS BEGIN -- IF getLevel(pCTX) > pLEVEL THEN -- oldversion IF getLevel(pCTX) >= pLEVEL THEN -- oldversion RETURN TRUE; ELSE RETURN FALSE; END IF; END islevelEnabled; |
From: <log...@li...> - 2003-12-16 22:00:53
|
Hello, This message is to inform you that we, the log4j developers, are actively considering the creation of a top level Apache project offering a wide-range of cross-language Logging Services. You are invited to join the discussion at the = log...@ja... mailing list. You can also follow the thread here http://marc.theaimsgroup.com/?t=3D107115526200001&r=3D1&w=3D2 If you decide to join the LS project, your project would become a sub-project of Logging Services. The Logging Services project is intended to regroup various logging related projects on equal footing under one umbrella and one banner. Please note that joining the Logging Services project would necessarily mean changing your existing license to the Apache Software License. You would be also expected to propose at least one representative to the Project Management Committee of the Logging Services project. Any such representative(s) would carry the primary responsibility to supervise your Logging Services sub-project. In accordance with Apache's traditional delegation model, the day-to-day management of your sub-project would be left to its developers. We have absolutely no intention or desire to micro-manage sub-projects. A draft of the project creation proposal can be found in our Wiki pages: http://nagoya.apache.org/wiki/apachewiki.cgi?LoggingApacheOrg/BoardResolu= ion --=20 Ceki G=FClc=FC For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp =20 |
From: <log...@li...> - 2003-11-27 09:22:55
|
When the following call is performed (after having appropriately initialised ctx) PLOG.setLevel(ctx); ORA-20501: Set Level not in LOG predefine constantes I have looked in the code and noticed that the pLEVEL is set to PLOG.NOLEVEL in that case. The problem is simply that in the following code of SetLevel IF pLEVEL <> LOFF AND pLEVEL <> LFATAL AND pLEVEL <> LERROR AND pLEVEL <> LWARN AND pLEVEL <> LINFO AND pLEVEL <> LDEBUG AND pLEVEL <> LALL THEN the following line is missing. pLEVEL <> NOLEVEL AND You might want to amend the code appropriately Sincerely luca |
From: <log...@li...> - 2003-11-23 10:22:22
|
on plog.init the third parameter is output to pipe and not log in transaction |
From: <log...@li...> - 2003-11-13 11:47:09
|
For information ---------------------- Hi,=20 =20 - currently is necessary to upgrade :=20 ReaderLogDataBase.sqlj (line 90, 130), pbolg.sql -> FUNCTION getLevelInText (line 1017) If I make the modification, have you the capability to test-it in 9i ? Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 -----Message d'origine----- De : jan-pieter Envoy=E9 : mercredi 12 novembre 2003 16:28 =C0 : MOULARD Guillaume OCISI Objet : Re: RE: LOG4PLSQL TNX for the scripts. I'll take a look at it this evening. We do use the Log4JbackgroundProcess. But unfortunately, 'fatal' doesn't = correspond with 'Notice'. And our firm has an other tool that monitors = all syslog of our unix server (100+),=20 unix/linux Level from low -> high Debug ( included ) Info ( included ) Notice=20 Warning ( included ) Err Crit Alert Emerg regz, JP6 ------------------------ >Hi,=20 > =20 > Sorry, the project don't use CVS. > > The first beta 3 is in attachement. > =20 > About yours custum level, perapse your level is equal to FATAL. > Do you use Log4JbackgroundProcess? > >Regards,=20 >Guillaume Moulard=20 >gmo...@us... > >Project : LOG4PLSQL : Oracle Database Loggin tools >see : http://log4plsql.sourceforge.net/ >=20 > >-----Message d'origine----- >De : jan-pieter >Envoy=E9 : mercredi 12 novembre 2003 14:45 >=C0 : gmo...@us... >Objet : LOG4PLSQL > > >HI 'gmoulard', > > >I want to help on your project but I foundn't the V3 scripts on the = CVS. > >Our firm uses alles severity levels in the syslog and not the 'FATAL'. > >Following levels would be very nice to have: > >-Notice ( for us very important) > >Other levels=20 >Crit >Alert >Emerg ( probably your fatal) > >If I can/may help, let me know, > > >With Kind Regards, > >JP6 > |
From: <log...@li...> - 2003-11-10 19:22:46
|
Herman,=20 =20 Line 327 in pblog, if you change by this line : pCTX.LSection :=3D = substr(pCTX.LSection,1,instr(UPPER(pCTX.LSection), UPPER(pSECTION), = -1)-2); You don't have a same problem ? Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : lundi 10 novembre 2003 15:07 =C0 : log...@li... Objet : [log4plsql] Problem with SetEndSection I have a package called test_controller. It has a procedure = 'controller'. When I call PLOG.SetBeginSection(pCTX, 'controller'); PLOG.debug(pCTX, 'test'); PLOG.SetEndSection(pCTX, 'controller'); The name in this section is: test_controller.controller. After SetEndSection, the name of the pCTX is 'test' instead of 'test_controller'. The EndSection routine looks for the first occurrence of 'controller' = and then takes the substring from the begin to one character before = controller: test_controller.controller controller test One way to do this is to search also for the dot: '.controller' instead of 'controller'. test_controller.controller .controller test_controller But this will stay a problem when two times the same sectionname is = used, 'controller': test_controller.controller.controller .controller Better would be to search for the last occurrence or a regexp like: \.controller$ I'm looking forward to a new release, allthough this is the only problem noticed so far. Herman Suijs =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Whitehorses B.V. Phone +31 26 3226900 Herman Suijs Mobile: +31 6 52002531 Postbus 4064 Fax: +31 26 3226909 6803 EB Arnhem Email her...@wh... ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
From: <log...@li...> - 2003-11-10 14:03:00
|
I have a package called test_controller. It has a procedure 'controller'. When I call PLOG.SetBeginSection(pCTX, 'controller'); PLOG.debug(pCTX, 'test'); PLOG.SetEndSection(pCTX, 'controller'); The name in this section is: test_controller.controller. After SetEndSection, the name of the pCTX is 'test' instead of 'test_controller'. The EndSection routine looks for the first occurrence of 'controller' and then takes the substring from the begin to one character before controller: test_controller.controller controller test One way to do this is to search also for the dot: '.controller' instead of 'controller'. test_controller.controller .controller test_controller But this will stay a problem when two times the same sectionname is used, 'controller': test_controller.controller.controller .controller Better would be to search for the last occurrence or a regexp like: \.controller$ I'm looking forward to a new release, allthough this is the only problem noticed so far. Herman Suijs =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Whitehorses B.V. Phone +31 26 3226900 Herman Suijs Mobile: +31 6 52002531 Postbus 4064 Fax: +31 26 3226909 6803 EB Arnhem Email her...@wh... |
From: <log...@li...> - 2003-09-09 09:39:00
|
Hi,=20 =20 For the next log4plsql release, we had develop a lot of new feature. - Do you have ideas of new functionalities for this version 3? - Please be to you beta tester of this version 3? =20 --------------------- -- new in log4plsql --------------------- News features =B7 Log in alert.log, trace file (thank to andreAs for information) =B7 Log with DBMS_OUTPUT (Wait -> SET SERVEROUTPUT ON) . Log full_call_stack =B7 getLOG4PLSQVersion return string Version =B7 getLevelInText return the text level for one level I read a very interesting article write by Steven Feuerstein in Oracle = Magazine =93Handling Exceptional Behavior=94 this 2 new features is = inspired direcly by this article =B7 assert procedure =B7 default message for each log procedure is now SQLCODE and SQLERRM Update =B7 Update default value of PLOGPARAM.DEFAULT_LEVEL -> DEBUG=20 =B7 Now is possible to log in table and in log4j =B7 ctx and init funtion parameter. =20 =B7 Create of PLOGPARAM for updatable parameter Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 |
From: <log...@li...> - 2003-06-27 10:06:51
|
Yo, I had to modify the code in Plog ( line 219 ) original DBMS_PIPE.pack_message(TO_CHAR(TO_CHAR(pLDATE, 'DD month YYYY HH24:MI:SS')||':'||TO_CHAR(MOD(pLHSECS,100),'09'))); now DBMS_PIPE.pack_message(TO_CHAR(pLDATE, 'DD month YYYY HH24:MI:SS')||':'||TO_CHAR(MOD(pLHSECS,100),'09')); this solves error message : PLS-00307: too many declarations of 'TO_CHAR' match Regz, JP |
From: <log...@li...> - 2003-06-23 12:28:57
|
Fran=E7ois,=20 Is not possible for me to test'it, but I find 2 differents exemple. In log4j FAQ I read the necesity to start in init.d file le syslogd = process with -r parameter ---------------------- -- log4j.xml ---------------------- <appender name=3D"SYS" class=3D"org.apache.log4j.net.SyslogAppender"> <param name=3D"Facility" value=3D"SYSLOG"/> <param name=3D"FacilityPrinting" value=3D"true"/> <param name=3D"SyslogHost" value=3D"111.222.3.44"/> <layout class=3D"org.apache.log4j.PatternLayout"> <param name=3D"ConversionPattern" value=3D"%d| %c| %X{to} | = %X{from} | %X{service} | %X{action} |%n"/> </layout> </appender> ----------------------- -- in log4j.properties ----------------------- # Set options for appender named "A1". # Appender "A1" will be a SyslogAppender log4j.appender.A1=3Dorg.apache.log4j.net.SyslogAppender # The syslog daemon resides on www.abc.net log4j.appender.A1.SyslogHost=3Dwww.abc.net # A1's layout is a PatternLayout, using the conversion pattern # <b>%r %-5p %c{2} %M.%L %x - %m\n</b>. Thus, the log output will # include # the relative time since the start of the application in # milliseconds, followed by the level of the log request, # followed by the two rightmost components of the logger name, # followed by the callers method name, followed by the line number, # the nested disgnostic context and finally the message itself. # Refer to the documentation of {@link PatternLayout} for further = information # on the syntax of the ConversionPattern key. log4j.appender.A1.layout=3Dorg.apache.log4j.PatternLayout log4j.appender.A1.layout.ConversionPattern=3D%-4r %-5p %c{2} %M.%L %x - = %m\n =20 Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : lundi 23 juin 2003 14:42 =C0 : log...@li... Objet : [Log4plsql] How to write in the Syslog file Hi, I have seen in the documentation that it is possible via the Log4JbackgroundProcess to use the standard features of log4j. My question is : Is it possible to have or where to found an example of = use of the Log4JbackgroundProcess an in particular in the case of the writing = in the syslog file. Thanks in advance. Regards, Fran=E7ois Geraerts ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
From: <log...@li...> - 2003-06-23 12:24:09
|
when you like to write directly to alert.log or a tracefile you can use = sys.dbms_system.ksdwrt(n,message);=20 where n is one of:=20 1 - writes message to trace file only.=20 2 - writes message to alert.log only.=20 3 - writes message to both alert.log and trace file.=20 yours sincerely andreAs -----Urspr=FCngliche Nachricht----- Von: log...@li... *EXTERN* [mailto:log...@li...] Gesendet: Montag, 23. Juni 2003 14:42 An: log...@li... Betreff: [Log4plsql] How to write in the Syslog file Hi, I have seen in the documentation that it is possible via the Log4JbackgroundProcess to use the standard features of log4j. My question is : Is it possible to have or where to found an example of = use of the Log4JbackgroundProcess an in particular in the case of the writing = in the syslog file. Thanks in advance. Regards, Fran=E7ois Geraerts ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting = Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly = Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Log4plsql-all-info mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net |
From: <log...@li...> - 2003-06-23 11:43:01
|
Hi, I have seen in the documentation that it is possible via the Log4JbackgroundProcess to use the standard features of log4j. My question is : Is it possible to have or where to found an example of use= of the Log4JbackgroundProcess an in particular in the case of the writing in the syslog file. Thanks in advance. Regards, Fran=E7ois Geraerts |
From: <log...@li...> - 2003-06-10 07:49:27
|
Hi,=20 =20 Project: LOG4PLSQL (log4plsql) Package: log4plsql Production Version (V2.1.1) Date : 2003-06-07 03:00 Project "LOG4PLSQL" ('log4plsql') has released the new version of = package 'log4plsql Production Version'. You can download it from SourceForge.net by = following this link: http://prdownloads.sourceforge.net/log4plsql/Log4plsql.zip=20 News features :=20 =B7 Add is[Debug|Info|Warn|Error|Fatal]Enabled requested by Dan Catalin =B7 Open a capability to decrease a level =B7 Create a fatal procedure for log Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 |
From: <log...@li...> - 2003-05-21 13:55:34
|
All information is in the attached file. |
From: <log...@li...> - 2003-04-28 15:02:20
|
Project : LOG4PLSQL has released the V2.1 version of package :=20 LOG4PLSQL is a free plsql generic tools for log, trace and=20 debug some message and variable in Oracle Database - Oracle Package, Procedure, Function, Trigger - PL/SQL Web application http://log4plsql.sourceforge.net LOG4PLSQL Objectives: - Easy of implemented and use=20 - Possibility to log off transaction=20 - Possibility to adapt the level of logging depending on user = requirements=20 - Ability to use all LOG4J feature. =20 LOG4PLSQL is free and easy to use :=20 |begin=20 | PLOG.info ('Yours loggin mess'); |End; =20 LOG4PLSQL Log destination=20 Oracle Table, Async,JDBC, JMS, NTEventLog, SMTP, Socket, SocketHub, = Syslog, Telnet, Writer Regards,=20 Guillaume Moulard=20 gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 |
From: <log...@li...> - 2003-03-18 08:51:54
|
Hi, Yes, is correct. And there is one proposition without dbms_pipe of the package by Dan Catalin. G. -----Message d'origine----- De : log...@li... = [mailto:log...@li...] Envoy=E9 : mardi 18 mars 2003 00:08 =C0 : log...@li... Objet : [Log4plsql] q: regarding transaction log off Hi , is it correct that you've choosen to use dbms_pipe instead of pragma = automuns_transaction to be more generic ?=20 (if you have the answer i'm a mailing list , a appolgize for the = repeating question ) -----Message d'origine----- De : log...@li... [mailto:log...@li...] Envoy=E9 : mercredi 13 novembre 2002 00:18 =C0 : log...@li... Objet : RE: [Log4plsql] dbms_pipe vs autonomus_transaction It seems to me more clear and easy to use and ... I saw some other = requests for this. Please find the changes attached. changes: renamed DEFAULT_USE_PIPE to DEFAULT_LOG_OFF_TRAN renamed all USE_PIPE occurrences to LOG_OFF_TRAN removed background* functions added two private procedures addRow addRowAutonomous changed log function to check LOF_OFF_TRAN and to call addRow or addRowAutonomous. =20 Please let me know if this is OK. If not I can make the changes you suggest. Should I add also other functions like isDebugEnabled() which exists in log4j? Thank you very much for your time. Dan Catalin -----Original Message----- From: log...@li... [mailto:log...@li...] Sent: Tuesday, November 12, 2002 06:27 AM To: log...@li... Subject: RE: [Log4plsql] dbms_pipe vs autonomus_transaction Bonjour,=20 I think : Why not. why your prefere autonomus_transaction versus dbms_pipe? Cordialement / Regards,=20 Guillaume Moulard=20 > -----Message d'origine----- > De : log...@li... > [mailto:log...@li...] > Envoy=E9 : vendredi 8 novembre 2002 21:15 > =C0 : log...@li... > Objet : [Log4plsql] dbms_pipe vs autonomus_transaction >=20 >=20 > Would be nice to be able to set how to log (using dbms_pipe=20 > or autonomus_transaction). >=20 > If the concern is 7.x does does not support this=20 > it would be nice to specify the version=20 > at the instalation time andthe install script will create the package=20 > with or without autonomus_transaction procedure in place. > What do you think? >=20 > Most of the times people nee to log outside of the current=20 > transaction=20 > and in the database, so the autonomus_transaction will be ok. >=20 > Catalin >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm=20 > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Log4plsql-all-info mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info > log4plsq : http://log4plsql.sourceforge.net |