|
From: Thomas M. <Tho...@un...> - 2003-03-12 10:50:19
|
Hi gurus, yesterday I had a look at this project and first thing I unfortunately noticed was that a SocketAppender is missing. I also browsed through the CVS and did not find anything. I also saw one or two RFEs and I think one or two postings requesting one so I really guess there is none :). I'd just like my logging to go somewhere else on screen. I quickly thought of some options I have: I could use "tail -f" but somehow I don't like the "lag". Then I could open another xterm, get the tty and tell a FileAppender to log there. But then again different xterms get different ttys and I don't wanna hack all my config files when this information changes. Btw, is there a way to tell an xterm the tty to use? Then I could use a fifo, tell a FileAppender to log there. This works fine if I have an xterm open with a "cat /tmp/fifo". But of course it sucks when I don't have it running because the open() call in FileAppender blocks. Of course this could be solved with an O_NONBLOCK but open flags do not seem to be configurable (I looked at PropertyConfiguratorImpl.cpp). So I quickly hacked a SocketAppender which sends logging output (albeit no serialized LoggingEvents due to obviuos reasons) to a socket and a little program I called sockcat which just dumps everything read from a socket (btw, does netcat have an option to "listen forever"? besides starting it in an endless loop?). This works but of course this is also not "property configurable". So I could waste^H^H^H^H^H invest some creative energy here. Would this be welcome and appreciated? Or, even better, do you know a quick solution to the above? advTHANKSance and regards, Thomas. -- Thomas Maier (Tho...@un...) |