JNI based Syslog appender
I have a requirement to develop a way in which audits are written to syslogd in Unix, but I am need to secure all ports, and would like to not leave port 514 open. The only way I know to do this is to develop a JNI based syslog appender using syslog.h. Does the log4J group have a need to this? Should I add it to my log4j CVS tree and submit a patch? please advise. thank you.
questions about the TODO list
I have a couple of questions concerning the TODO list. They involve the following entries: - SSL logging. - Authenticated logging. Could someone better explain them? Does the "SSL Logging" mean that you want log4j to write messages to another process using SSL? Or does it mean posting the data to an SSL based web page in the form of a multi-part request? I have extensive experience writing SSL code in java and would like some guidance on this so I may help. As far as the "Authenticated logging", does this mean that you want to log over ssh? This one I am a little more confused on. Has anyone else done any work on these? Please advise. Thank you.
Prototype written : JNI Syslog appender
I have written a JNI based syslog appender. I would like to submit this code to the group for approval. Is there a formal process for doing so? thank you.
Re: Re: Prototype written : JNI Syslog appender
First off, I want to thank you for the response and direction. Here are the files that I think you need. - jnisyslog.tar.gz contain the java file and the C file. Inside this file there is also a test directory, which contains a test program and .lcf file that is called by the test.jnisyslog target in the build.xml changes I have made. - build.xml.diff if the output of the following command "cvs diff -u build.xml > build.xml.diff" Let me know if you need anything else. I think that I have explained everything you would need in the javadocs. Please let me know if this will make it into the baseline. Thanks again ! ---Original Message--- > From: Paul Smith <[EMAIL PROTECTED]> > Subject: Re: Prototype written : JNI Syslog appender > Sent: 29 Feb 2004 21:45:33 > > On Sun, 2004-02-29 at 14:36, log4jdev wrote: > > I have written a JNI based syslog appender. I would like to submit > > this code to the group for approval. Is there a formal process for > > doing so? > > Apologise for the brevity of this email, I'm a bit snowed under: > > * Please conform to the Log4j coding conventions, if you use Jalopy, you > can use the log4j-coding-conventions.xml file under the src/jalopy > directory of the Log4j CVS module. > > * Documentation within the main java file is incredibly important, with > any notes as to configuration etc to get it working. > > * Post your files to a new Bugzilla item. (this prevents it from getting > lost) - ideally its in the "diff -u" format, but since it's probably all > new files, the new java file, or zip up multiple. > > * Also post the above to the log4j-dev list for review. > > regards, > > Paul Smith ---Original Message--- jnisyslog.tar.gz Description: Binary data build.xml.diff Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Prototype written : JNI Syslog appender
one more point to note. jnisyslog.tar.gz should be extracted to the logging-log4j/src/java/org/apache/log4j directory. :) ---Original Message--- > From: log4jdev <[EMAIL PROTECTED]> > Subject: Re: Re: Prototype written : JNI Syslog appender > Sent: 01 Mar 2004 17:25:57 > > First off, I want to thank you for the response and direction. > > Here are the files that I think you need. > - jnisyslog.tar.gz contain the java file and the C file. Inside this file there is also a test directory, which contains a test program and .lcf file that is called by the test.jnisyslog target in the build.xml changes I have made. > - build.xml.diff if the output of the following command "cvs diff -u build.xml > build.xml.diff" > > Let me know if you need anything else. I think that I have explained everything you would need in the javadocs. > > Please let me know if this will make it into the baseline. > > Thanks again ! > > > ---Original Message--- > > From: Paul Smith <[EMAIL PROTECTED]> > > Subject: Re: Prototype written : JNI Syslog appender > > Sent: 29 Feb 2004 21:45:33 > > > > On Sun, 2004-02-29 at 14:36, log4jdev wrote: > > > I have written a JNI based syslog appender. I would like to submit > > > this code to the group for approval. Is there a formal process for > > > doing so? > > > > Apologise for the brevity of this email, I'm a bit snowed under: > > > > * Please conform to the Log4j coding conventions, if you use Jalopy, you > > can use the log4j-coding-conventions.xml file under the src/jalopy > > directory of the Log4j CVS module. > > > > * Documentation within the main java file is incredibly important, with > > any notes as to configuration etc to get it working. > > > > * Post your files to a new Bugzilla item. (this prevents it from getting > > lost) - ideally its in the "diff -u" format, but since it's probably all > > new files, the new java file, or zip up multiple. > > > > * Also post the above to the log4j-dev list for review. > > > > regards, > > > > Paul Smith > ---Original Message--- > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] ---Original Message---
question on becoming a log4j developer
I have been interested in log4j for some time. I have written many programs that use log4j, and have even submitted code for a new Appender (JniSyslogAppender). I have not recieved any email back from the group on this proposed enhancement. As someone who wants to help out with the log4j development, I have a few question 1. Are there many developers working log4j? There do not seem to be alot of people using this mailing list. 2. Is this the right forum to get questions answered? I posted a message with some questions on the TODO list and never to a response. thank you for your time. ...Mark
Re: RE: question on becoming a log4j developer
Thank you for getting back to me. I agree that life can get pretty hectic. I fall in to the category of having a full time job. I am most interested in finding out what the status of my feature submission is. I have followed the advice of the group and have not gotten any response. I do not know if this means that the code I submitted was good, bad, no one has looked at it or no one has interest in it. I hope I can be of some help on this project, as I am looking to break into the open source programming world after 5 years of java development experience. ---Original Message--- > From: Shapira, Yoav <[EMAIL PROTECTED]> > Subject: RE: question on becoming a log4j developer > Sent: 04 Mar 2004 14:15:54 > > Hi, > > >1. Are there many developers working log4j? There do not seem to be > alot of >people using this mailing list. > > See http://logging.apache.org/log4j/docs/contributors.html. Not > everyone is active at the same time, as we all (AFAIK) have full-time / > $$$ jobs. Also, different people tend to work with different parts of > the framework. > > Log4j since 1.2.8 has been very stable, which is not surprising > considering it's a very well-defined API with little scope creep and > many users who've been using it in production for a long time. That's > why there hasn't been as much traffic on this list in 2003/2004 (so > far), as compared to 2001-2002 for example. > > As log4j 1.3 is nearing an alpha release, I expect the volume of traffic > on both this and the log4j-user list to increase significantly. As will > development activity. > > >2. Is this the right forum to get questions answered? I posted a > message >with some questions on the TODO list and never to a response. > > Development questions, yes. As to why people never responded, the > general answer is well-phrased in > http://jakarta.apache.org/tomcat/faq/tomcatuser.html#why. I don't > remember your message, so I can't remember why I personally didn't > respond to it ;) > > Yoav Shapira > > > > This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] ---Original Message---
