RE: Four questions (about logging, connectors and manager)
A #2: I don't feel the connectors are complex. JK is easy to configure, easy to get working (once you understand how it works), and stable. If you don't want to use a connector, don't even deal with mod_rewrite or mod_proxy, just run Tomcat on port 80 and be done with it. Or better yet, run it on 8080 and use iptables/ipchains to redirect 80 to 8080. John -Original Message- From: Tomasz Nowak [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 9:33 AM To: [EMAIL PROTECTED] Subject: Four questions (about logging, connectors and manager) Hello. I have four questions for which I could not find any good answers in web, usenet gruops or this mailing-list archive. Q #1 Tomcat logs HTTP errors (ie 404 File Not Found) in access_log with other regulary HTTP status codes. It does it in: a) its own access_log (org.apache.catalina.valves.AccessLogValve) as well as b) in Apache HTTPD's access_log when connected via mod_jk/jk2 But is there any facility to split errors to separate error_log file in the manner that Apache HTTPd does? a) in inner-Tomcat error_log, or b) in Apache HTTPD's error_log when connected via mod_jk/jk2 (even better) Q #2 Why exectly are connectors used to redirect requests from webserver to Tomcat and why are they so complex not to say complicated? I now that load balancing is sometimes important, but I believe in most cases people use one-to-one connection (one worker, one tomcat). So what about mod_rewriting 8080 to 80 instead of a connector then? What are pros and cons of rewriting instead of using a connector? What justifies its complexibility? Q #3 Is there any possibility to manage (with built-in manager webapp) all engine's webapps (contexts)? I mean not specific vhost webapps, but all vhosts and their webapps at once? Q #4 What alternative software (maybe dekstop-type?) would you recommend for managing webapps? Thank you in advance. -- Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Four questions (about logging, connectors and manager)
Turner, John [EMAIL PROTECTED] wrote: A #2: I don't feel the connectors are complex. JK is easy to configure, easy to get working (once you understand how it works), and stable. Hi, John. Browsing the archive I've remebered you as a very competent developer/user, so I'm really very glad you answered my letter :) I would like to tell you about mod_jk complexibility and stability from my point of view. 1. Starting Tomcat 4.1.18 with org.apache.ajp.tomcat4.Ajp13Connector, catalina.out: ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:369) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:777) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:751) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:339) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLifecycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Tada! Seems they dont like with JMX each other. 2. But let's request some simple pages (ROOT/index.jsp couple of times, list webapp in manager, etc). Pages in fact work well, but after only a few requests I find in logs such a mess: catalina.out: java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END at java.nio.charset.CharsetEncoder.throwIllegalStateException(CharsetEncoder.java:933) at java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:529) at sun.nio.cs.StreamEncoder$CharsetSE.flushLeftoverChar(StreamEncoder.java:356) at sun.nio.cs.StreamEncoder$CharsetSE.implClose(StreamEncoder.java:412) at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:158) at java.io.OutputStreamWriter.close(OutputStreamWriter.java:222) at java.io.PrintWriter.close(PrintWriter.java:137) at org.apache.catalina.connector.ResponseBase.finishResponse(ResponseBase.java:483) at org.apache.catalina.connector.HttpResponseBase.finishResponse(HttpResponseBase.java:253) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:191) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:536) (x12 times) engine log: === java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:536) (multiple) 2003-02-27 16:01:47 Ajp13Processor[8009][1] process: invoke java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.ajp.Ajp13.send(Ajp13.java:525) at org.apache.ajp.RequestHandler.finish(RequestHandler.java:501) at org.apache.ajp.Ajp13.finish(Ajp13.java:395) at org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:196) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:464) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at
RE: Four questions (about logging, connectors and manager)
I'm sorry, I didn't realize you were going to argue with me and criticize my reply. I thought you were asking for an opinion. First, Ajp13Connector is not the recommended connector to use for 4.1.18. CoyoteConnector is the recommended connector. Second, the compatibility problems between Ajp13Connector and JMX are well-known, at least on this list. Since you seem so adept at searching the list, I'm sure you would have seen this. Third, we have several production sites right now with 4.1.18, Apache 2, and mod_jk. We have a couple dozen more with Apache 1.3, mod_jserv, and Tomcat 3.x. All are under fairly heavy load, approx. 100,000 page views per day during the week. The apps are all heavily graphic-intensive, that is, lots of file I/O, lots of RAM, lots of CPU. We don't have any problems with mod_jserv or mod_jk. Uptime is in the many months timeframe, each and every site and webapp is monitored for availability every 60 seconds, 24/7 and there have been no alerts that weren't initiated by us for maintenance...I consider that stable. You may not. You may have problems, I can only reply to your questions with comments and opinions based on my personal experience. If you don't like that, my advice is to refrain from posting the question in the first place, or, if you must post, clearly state in your post the parameters within which you will consider a reply to be valid such as I want your opinion, but only if you agree with me. Fourth, you've got some Charset errors in there. Our apps don't use anything but standard Western charsets (our apps are all in English except for a few that are in French), so I am not familiar with those errors. I don't think I would blame them on JK, though. Fifth, I'm not a developer. I'm a systems administrator. It's simple: if you don't want to use a connector, THEN DON'T. Nobody is twisting your arm, and the use of Apache with Tomcat is NOT REQUIRED. Arguing about connector stability or problems is a waste of time...they're open source. Either pitch in and fix them to your heart's content, help others to do so, or be quiet. If you must use Apache with Tomcat for some reason, there are a number of ways to do this, all of which have been discussed to death on this list, and if I had to rank them I would rank them thusly: 1) JK, 2) JK2, 3) mod_proxy/mod_rewrite, 4) external redirection (ipchains, for example, or some other software). I doubt anyone will tell you differently, but I've been wrong plenty of times before and you are certainly welcome to disagree. Perhaps others will answer your other questions. Arguing is a waste of my time, I apologize for replying in the first place and wasting yours. John -Original Message- From: Tomasz Nowak [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 10:28 AM To: Tomcat Users List Subject: Re: Four questions (about logging, connectors and manager) Turner, John [EMAIL PROTECTED] wrote: A #2: I don't feel the connectors are complex. JK is easy to configure, easy to get working (once you understand how it works), and stable. Hi, John. Browsing the archive I've remebered you as a very competent developer/user, so I'm really very glad you answered my letter :) I would like to tell you about mod_jk complexibility and stability from my point of view. 1. Starting Tomcat 4.1.18 with org.apache.ajp.tomcat4.Ajp13Connector, catalina.out: ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:224) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean s(ServerLifecycleListener.java:369) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean s(ServerLifecycleListener.java:777) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean s(ServerLifecycleListener.java:751) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBean s(ServerLifecycleListener.java:339) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEv ent(ServerLifecycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(L ifecycleSupport.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.j ava:2182) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324
Re: Four questions (about logging, connectors and manager)
Turner, John [EMAIL PROTECTED] wrote: Arguing is a waste of my time. That is very true! Believe me or not, but I really didn't want to argue with you, John. 1. I asked why is it so complex?. 2. You answered that it isn't complex that for you and said that it is stable 3. So I presented an evidence justifing _my point of view_ (why it seems so complex or even unstable for me) 4. So you presented your evidence that it is stable indeed (we have several production sites right now...) Why do you call such discusion an argue? First, Ajp13Connector is not the recommended connector to use for 4.1.18. CoyoteConnector is the recommended connector. But on the other hand mod_jk2 is not the recommended connector to use for Apache 1.3. mod_jk is the recommended, isn't it? ;) There are some reasons I can't upgrade Apache HTTPd to ver 2 right now. But OK, I will try to use mod_jk2 if you recommend it. Second, the compatibility problems between Ajp13Connector and JMX are well-known, at least on this list. Since you seem so adept at searching the list, I'm sure you would have seen this. Yep. That's why I knew what causes such error. [...] I can only reply to your questions with comments and opinions based on my personal experience. So I suppose you don't mind my questions being based on my personal experience (and even evidence them), do you? ;) Fourth, you've got some Charset errors in there. Our apps don't use anything but standard Western charsets (our apps are all in English except for a few that are in French), so I am not familiar with those errors. I don't think I would blame them on JK, though. JSP pages work very well via http11 connector. When I deploy jk/ajp3 connection - these erros apear in tomcat logs. What else then JK shell I blame for these errors? Arguing about connector stability or problems is a waste of time...they're open source. Either pitch in and fix them to your heart's content, help others to do so, or be quiet. I am not a programmer and I can't fix bugs in JK by myself. But I always try to contribuite to Open Source activities as much as I can. Tracking potential bugs and building archives of problem solutions is also kind of contribution IMHO. I had to rank them I would rank them thusly: 1) JK, 2) JK2, 3) mod_proxy/mod_rewrite, 4) external redirection This is also my rank, John. That's why tried mod_jk, not mod_jk2 first. -- Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Four questions (about logging, connectors and manager)
My point about the connectors was that, in server.xml, you should DISABLE Ajp13Connector and ENABLE CoyoteConnector on port 8009. CoyoteConnector supports both JK and JK2 *and HTTP and HTTPS). So, you can use Apache 1.3, mod_jk, but then on the Tomcat side choose CoyoteConnector instead of Ajp13Connector. CoyoteConnector is enabled by default...just reverse the change you made in server.xml. John -Original Message- From: Tomasz Nowak [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 12:12 PM To: Tomcat Users List Subject: Re: Four questions (about logging, connectors and manager) Turner, John [EMAIL PROTECTED] wrote: First, Ajp13Connector is not the recommended connector to use for 4.1.18. CoyoteConnector is the recommended connector. But on the other hand mod_jk2 is not the recommended connector to use for Apache 1.3. mod_jk is the recommended, isn't it? ;) There are some reasons I can't upgrade Apache HTTPd to ver 2 right now. But OK, I will try to use mod_jk2 if you recommend it. Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Four questions (about logging, connectors and manager)
Should I be using the AJP1.3 connector for the mod_jk and apache I just setup (1.3.27), or should I be using the coyote connector? I did try the coyote connector, but couldn't seem to get it to connect. The AJP1.3 connector seems to work perfectly for me once I disabled the JMX stuff. --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 9:20 AM To: 'Tomcat Users List' Subject: RE: Four questions (about logging, connectors and manager) My point about the connectors was that, in server.xml, you should DISABLE Ajp13Connector and ENABLE CoyoteConnector on port 8009. CoyoteConnector supports both JK and JK2 *and HTTP and HTTPS). So, you can use Apache 1.3, mod_jk, but then on the Tomcat side choose CoyoteConnector instead of Ajp13Connector. CoyoteConnector is enabled by default...just reverse the change you made in server.xml. John -Original Message- From: Tomasz Nowak [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 12:12 PM To: Tomcat Users List Subject: Re: Four questions (about logging, connectors and manager) Turner, John [EMAIL PROTECTED] wrote: First, Ajp13Connector is not the recommended connector to use for 4.1.18. CoyoteConnector is the recommended connector. But on the other hand mod_jk2 is not the recommended connector to use for Apache 1.3. mod_jk is the recommended, isn't it? ;) There are some reasons I can't upgrade Apache HTTPd to ver 2 right now. But OK, I will try to use mod_jk2 if you recommend it. Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Four questions (about logging, connectors and manager)
If it works, I say go for it and call it good...you've got an unusual beast there (Unixware). Common setups for other operating systems might not work for you, so you should go with what works. John -Original Message- From: Mike Jackson [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 12:24 PM To: Tomcat Users List Subject: RE: Four questions (about logging, connectors and manager) Should I be using the AJP1.3 connector for the mod_jk and apache I just setup (1.3.27), or should I be using the coyote connector? I did try the coyote connector, but couldn't seem to get it to connect. The AJP1.3 connector seems to work perfectly for me once I disabled the JMX stuff. --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 9:20 AM To: 'Tomcat Users List' Subject: RE: Four questions (about logging, connectors and manager) My point about the connectors was that, in server.xml, you should DISABLE Ajp13Connector and ENABLE CoyoteConnector on port 8009. CoyoteConnector supports both JK and JK2 *and HTTP and HTTPS). So, you can use Apache 1.3, mod_jk, but then on the Tomcat side choose CoyoteConnector instead of Ajp13Connector. CoyoteConnector is enabled by default...just reverse the change you made in server.xml. John -Original Message- From: Tomasz Nowak [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 12:12 PM To: Tomcat Users List Subject: Re: Four questions (about logging, connectors and manager) Turner, John [EMAIL PROTECTED] wrote: First, Ajp13Connector is not the recommended connector to use for 4.1.18. CoyoteConnector is the recommended connector. But on the other hand mod_jk2 is not the recommended connector to use for Apache 1.3. mod_jk is the recommended, isn't it? ;) There are some reasons I can't upgrade Apache HTTPd to ver 2 right now. But OK, I will try to use mod_jk2 if you recommend it. Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Four questions (about logging, connectors and manager)
Turner, John [EMAIL PROTECTED] wrote: My point about the connectors was that, in server.xml, you should DISABLE Ajp13Connector and ENABLE CoyoteConnector on port 8009. CoyoteConnector supports both JK and JK2 *and HTTP and HTTPS). So, you can use Apache 1.3, mod_jk, but then on the Tomcat side choose CoyoteConnector instead of Ajp13Connector. CoyoteConnector is enabled by default...just reverse the change you made in server.xml. !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- ^^^ That had mistaken me! :) - I thought is was only for JK2 I've just removed Ajp13Connector and deployed CoyoteConnector and indeed it works much better. After 5 minutes of tests I don't see any strange errors in tomcat/logs. There is only one error message in httpd mod_jk.log: --- [Thu Feb 27 18:41:29 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems --- I looks that is somehow connected with this catalina.out message: --- Feb 27, 2003 6:41:29 PM org.apache.jk.common.ChannelSocket processConnection INFO: Server has been restarted or reset this connection --- which I don't understand exactly (maybe it is because I use it for the first time)? BTW: which JkLogLevel is more verbose: info or error? Info is usually used to get more verbose output then error, does it work differently in JK? Anyway, thanks for all your hints till now, John. -- Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Four questions (about logging, connectors and manager)
LOL, that's true enough, I'll stop now. However, just as an FYI, I'm playing with Unixware 7.1.3, which will be my next upgrade. It's got the ability to run linux applications natively, so I'll probably be able to get a normal configuration working when I feel comfortable with 7.1.3. It's kinda interesting, the install installs the standard unixware kernel and support files and then installs about 0.5-1.0 gig of linux support files. If I was to guess it kinda looks like it's installing a fairly complete linux kernel that it somehow runs in parallel to the unixware kernel. If it work well then I'll be able to get beyond jdk1.3.0_02 (their implementation of 1.3.1 is broken), will be able to run oracle 9i, and still be able to run the optical jukebox software (doesn't run under linux, the developer says that the scsi implementation on linux is badly broken and needs to be completely rewritten). Needless to say I've got my fingers crossed. Of course if the boss was willing to support Solaris this'd all be a moot point as everything I need will run on solaris (not on intel, on sparc). --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 9:25 AM To: 'Tomcat Users List' Subject: RE: Four questions (about logging, connectors and manager) If it works, I say go for it and call it good...you've got an unusual beast there (Unixware). Common setups for other operating systems might not work for you, so you should go with what works. John -Original Message- From: Mike Jackson [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 12:24 PM To: Tomcat Users List Subject: RE: Four questions (about logging, connectors and manager) Should I be using the AJP1.3 connector for the mod_jk and apache I just setup (1.3.27), or should I be using the coyote connector? I did try the coyote connector, but couldn't seem to get it to connect. The AJP1.3 connector seems to work perfectly for me once I disabled the JMX stuff. --mikej -=- mike jackson [EMAIL PROTECTED] -Original Message- From: Turner, John [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 9:20 AM To: 'Tomcat Users List' Subject: RE: Four questions (about logging, connectors and manager) My point about the connectors was that, in server.xml, you should DISABLE Ajp13Connector and ENABLE CoyoteConnector on port 8009. CoyoteConnector supports both JK and JK2 *and HTTP and HTTPS). So, you can use Apache 1.3, mod_jk, but then on the Tomcat side choose CoyoteConnector instead of Ajp13Connector. CoyoteConnector is enabled by default...just reverse the change you made in server.xml. John -Original Message- From: Tomasz Nowak [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 12:12 PM To: Tomcat Users List Subject: Re: Four questions (about logging, connectors and manager) Turner, John [EMAIL PROTECTED] wrote: First, Ajp13Connector is not the recommended connector to use for 4.1.18. CoyoteConnector is the recommended connector. But on the other hand mod_jk2 is not the recommended connector to use for Apache 1.3. mod_jk is the recommended, isn't it? ;) There are some reasons I can't upgrade Apache HTTPd to ver 2 right now. But OK, I will try to use mod_jk2 if you recommend it. Tomasz Nowak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
