Re: [AOLSERVER] exec in AOLserver
On Wednesday 09 June 2004 00:51, you wrote: Zoran, Ok I tried [exec /bin/csh -c /opt/myscript] and I get the same error. I also tried launching aolserver from /bin/csh instead of bash and I still had the same problem. Oh... I must say that I had the same problem with one of the older SuSE (7.3) releases. It apparently has nothing to do with the trapping of the SIGCHLD signal. What I did is to set breakpoints on all signal-related calls and then launch the nsd executable under debugger. Now, there are no places in the code which mingle with SIGCHLD signal whatsoever. I ran the vanilla AS distro, which means no extra modules apart from AS standard ones (nssock, nsperm, nslog). By running the server from /bin/csh the signal problem went away. It does not happen in your setup. Hm... So, there is something else wrong there... I will have to see wether I can find something. It has definitely something to do with the Linux OS. To make it even more interesting, even the plain tclsh executable on that system seems to have the same problem: mickey:/tmp # tclsh % exec ls kde-root ksocket-root lexxsrv.adr mcop-root run-crons.EDjFSK run-crons.o9xwkI run-crons.rIVDf9 error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) Strange... Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
On Wednesday 09 June 2004 00:51, you wrote: Zoran, Ok I tried [exec /bin/csh -c /opt/myscript] and I get the same error. I also tried launching aolserver from /bin/csh instead of bash and I still had the same problem. I did some more testing on our troublesome machine which behaves as yours, regarding the SIGCGHLD signal. You won't believe it... 1. I boot the Linux 2. Log into the console 3. Start AS - works fine 4. Stop AS 5. I log into over SSH 6. Start AS - failure to do exec !! 7. Stop AS 8. Log into the console again 9. Start AS - failure to do exec !! 10. Reboot the Linux 11. Log into console 12. Start AS - works fine The only conclusion I made out of this is that sshd does something wrong *system-wide* which brings problems with SIGCGHLD handling. Only when I reboot the system and *never* log-in using ssh the problem seems to be gone! Now, I really do not understand why. Now, this is happening on one of our machines running SuSE 7.3 Linux. I was not able to reproduce this on other machines. This all may not be the case at your site, but you never know. If possible try this out and see if this helps. Still I'm very confused... Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
I didn't mention that I was running on solaris 2.8 - based on Zoran's findings, that could be the discriminator. What specific OS version are you using and what JDK version? -Elizabeth Nathaniel H wrote on 6/8/04, 7:02 PM: Commenting out nsjk2 in the config turns off nsjk2. I can exec after that. Looks like the jvm (or something else?) is catching SIGCHLD I've got Tomcat 4.1.29 AOLserver 4.0.1 nsjk2 1.3 I'll have to try 4.0.3 next. -Nate I'm not sure its explained by just by virtue of the jvm running. I have an out-of-the-box 4.0.3 running nsjk2 v1.3 with Tomcat 4.1.27 and am able to successfully exec both commands below (I ran them from the control port) When I get a chance I will try and run a test with 4.0.1 and see if it behaves differently. -Elizabeth Barry Books wrote on 6/8/04, 3:10 PM: I have not tracked it specifically to the Oracle libs but that's my best guess. I'm not running the nsjk2 module. Currently I got around the problem by building the TCL Posix signal routines and reseting the signal. I think I've other discussion about the jvm catching SIGCHLD. On Tuesday, June 08, 2004, at 12:14PM, Dossy [EMAIL PROTECTED] wrote: On 2004.06.08, Nathaniel H [EMAIL PROTECTED] wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. This sounds exactly like the problem that Barry Books reported earlier on this list about nsora and exec. The newer Oracle client library apparently either installs its own SIGCHLD signal handler, or throws SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, therefore when Tcl's [exec] executes something, it wants to be able to catch the SIGCHLD of the child process when it dies. Unfortunately, the signal gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains about it. I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler replacing Tcl's handler. I don't know enough about nsjk2 or the various JVMs to know the answer to this. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
I didn't mention that I am running redhat 7.3 with java version 1.4.2_03. Now you know. My findings do not jive with Zoran's findings. I can run both of the execs mentioned before in the tcl interpreter. The tcl interpreter is the one that compiles with aolserver and it is verrsion 8.4. Since I can't run [exec /bin/bash -c /opt/myscript] when nsjk2 is active and I can when nsjk2 is inactive I am lead to believe this problem is nsjk2 related. 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] Number 1 works even when nsjk2 is active. Number 2 only works when nsjk2 is inactive. I'm not sure what is going on behind the scenes here. Number one runs /bin/ls and 2 is a shell script. -Nate I didn't mention that I was running on solaris 2.8 - based on Zoran's findings, that could be the discriminator. What specific OS version are you using and what JDK version? -Elizabeth Nathaniel H wrote on 6/8/04, 7:02 PM: Commenting out nsjk2 in the config turns off nsjk2. I can exec after that. Looks like the jvm (or something else?) is catching SIGCHLD I've got Tomcat 4.1.29 AOLserver 4.0.1 nsjk2 1.3 I'll have to try 4.0.3 next. -Nate I'm not sure its explained by just by virtue of the jvm running. I have an out-of-the-box 4.0.3 running nsjk2 v1.3 with Tomcat 4.1.27 and am able to successfully exec both commands below (I ran them from the control port) When I get a chance I will try and run a test with 4.0.1 and see if it behaves differently. -Elizabeth Barry Books wrote on 6/8/04, 3:10 PM: I have not tracked it specifically to the Oracle libs but that's my best guess. I'm not running the nsjk2 module. Currently I got around the problem by building the TCL Posix signal routines and reseting the signal. I think I've other discussion about the jvm catching SIGCHLD. On Tuesday, June 08, 2004, at 12:14PM, Dossy [EMAIL PROTECTED] wrote: On 2004.06.08, Nathaniel H [EMAIL PROTECTED] wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. This sounds exactly like the problem that Barry Books reported earlier on this list about nsora and exec. The newer Oracle client library apparently either installs its own SIGCHLD signal handler, or throws SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, therefore when Tcl's [exec] executes something, it wants to be able to catch the SIGCHLD of the child process when it dies. Unfortunately, the signal gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains about it. I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler replacing Tcl's handler. I don't know enough about nsjk2 or the various JVMs to know the answer to this. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED
Re: [AOLSERVER] exec in AOLserver
On Wednesday 09 June 2004 17:23, you wrote: I didn't mention that I am running redhat 7.3 with java version 1.4.2_03. Now you know. My findings do not jive with Zoran's findings. I can run both of the execs mentioned before in the tcl interpreter. The tcl interpreter is the one that compiles with aolserver and it is verrsion 8.4. Since I can't run [exec /bin/bash -c /opt/myscript] when nsjk2 is active and I can when nsjk2 is inactive I am lead to believe this problem is nsjk2 related. 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] Number 1 works even when nsjk2 is active. Number 2 only works when nsjk2 is inactive. I'm not sure what is going on behind the scenes here. Number one runs /bin/ls and 2 is a shell script. Now the confusion is perfect :) It might be worth to try on some other RH version. I have both RH 7.3 and 9.0 here and on the 9.0 I can't reproduce your problem. On the 7.3 however I could reproduce it with pure tclsh w/o any AS nor java involved. Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] exec in AOLserver
AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. Thanks, Nate -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
On 2004.06.08, Nathaniel H [EMAIL PROTECTED] wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. This sounds exactly like the problem that Barry Books reported earlier on this list about nsora and exec. The newer Oracle client library apparently either installs its own SIGCHLD signal handler, or throws SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, therefore when Tcl's [exec] executes something, it wants to be able to catch the SIGCHLD of the child process when it dies. Unfortunately, the signal gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains about it. I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler replacing Tcl's handler. I don't know enough about nsjk2 or the various JVMs to know the answer to this. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
I have not tracked it specifically to the Oracle libs but that's my best guess. I'm not running the nsjk2 module. Currently I got around the problem by building the TCL Posix signal routines and reseting the signal. I think I've other discussion about the jvm catching SIGCHLD. On Tuesday, June 08, 2004, at 12:14PM, Dossy [EMAIL PROTECTED] wrote: On 2004.06.08, Nathaniel H [EMAIL PROTECTED] wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. This sounds exactly like the problem that Barry Books reported earlier on this list about nsora and exec. The newer Oracle client library apparently either installs its own SIGCHLD signal handler, or throws SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, therefore when Tcl's [exec] executes something, it wants to be able to catch the SIGCHLD of the child process when it dies. Unfortunately, the signal gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains about it. I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler replacing Tcl's handler. I don't know enough about nsjk2 or the various JVMs to know the answer to this. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
I'm not sure its explained by just by virtue of the jvm running. I have an out-of-the-box 4.0.3 running nsjk2 v1.3 with Tomcat 4.1.27 and am able to successfully exec both commands below (I ran them from the control port) When I get a chance I will try and run a test with 4.0.1 and see if it behaves differently. -Elizabeth Barry Books wrote on 6/8/04, 3:10 PM: I have not tracked it specifically to the Oracle libs but that's my best guess. I'm not running the nsjk2 module. Currently I got around the problem by building the TCL Posix signal routines and reseting the signal. I think I've other discussion about the jvm catching SIGCHLD. On Tuesday, June 08, 2004, at 12:14PM, Dossy [EMAIL PROTECTED] wrote: On 2004.06.08, Nathaniel H [EMAIL PROTECTED] wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. This sounds exactly like the problem that Barry Books reported earlier on this list about nsora and exec. The newer Oracle client library apparently either installs its own SIGCHLD signal handler, or throws SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, therefore when Tcl's [exec] executes something, it wants to be able to catch the SIGCHLD of the child process when it dies. Unfortunately, the signal gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains about it. I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler replacing Tcl's handler. I don't know enough about nsjk2 or the various JVMs to know the answer to this. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
On Tuesday 08 June 2004 18:15, you wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. You are running Linux (I suppose you are) right? Please try switching to /bin/csh shell and then start the AOLserver from it and not the standard /bin/bash (or /bin/sh which is the same) and tell us what you get. I know it may seem silly at the first glance, but please do try. Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
Zoran, Ok I tried [exec /bin/csh -c /opt/myscript] and I get the same error. I also tried launching aolserver from /bin/csh instead of bash and I still had the same problem. Nate On Tuesday 08 June 2004 18:15, you wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. You are running Linux (I suppose you are) right? Please try switching to /bin/csh shell and then start the AOLserver from it and not the standard /bin/bash (or /bin/sh which is the same) and tell us what you get. I know it may seem silly at the first glance, but please do try. Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] exec in AOLserver
Commenting out nsjk2 in the config turns off nsjk2. I can exec after that. Looks like the jvm (or something else?) is catching SIGCHLD I've got Tomcat 4.1.29 AOLserver 4.0.1 nsjk2 1.3 I'll have to try 4.0.3 next. -Nate I'm not sure its explained by just by virtue of the jvm running. I have an out-of-the-box 4.0.3 running nsjk2 v1.3 with Tomcat 4.1.27 and am able to successfully exec both commands below (I ran them from the control port) When I get a chance I will try and run a test with 4.0.1 and see if it behaves differently. -Elizabeth Barry Books wrote on 6/8/04, 3:10 PM: I have not tracked it specifically to the Oracle libs but that's my best guess. I'm not running the nsjk2 module. Currently I got around the problem by building the TCL Posix signal routines and reseting the signal. I think I've other discussion about the jvm catching SIGCHLD. On Tuesday, June 08, 2004, at 12:14PM, Dossy [EMAIL PROTECTED] wrote: On 2004.06.08, Nathaniel H [EMAIL PROTECTED] wrote: AOlserver 4.0.0 to AOlserver 4.0.1 introduces an exec problem. On 4.0.0 I can run both: 1. [exec /bin/bash -c ls -al] 2. [exec /bin/bash -c /opt/myscript] But on AOLserver 4.0.1 (with nsjk2) number 2. fails with this error. error waiting for process to exit: child process lost (is SIGCHLD ignored or trapped?) while executing You should also know that, thanks to Elizabeth nsjk2, I am running nsjk2 on the problem 4.0.1 version. This sounds exactly like the problem that Barry Books reported earlier on this list about nsora and exec. The newer Oracle client library apparently either installs its own SIGCHLD signal handler, or throws SIGCHLD itself. This interferes with Tcl's SIGCHLD handler, therefore when Tcl's [exec] executes something, it wants to be able to catch the SIGCHLD of the child process when it dies. Unfortunately, the signal gets handled elsewhere, so Tcl doesn't see it, and thus [exec] complains about it. I'm guessing that nsjk2 or the JVM, too, installs a SIGCHLD handler replacing Tcl's handler. I don't know enough about nsjk2 or the various JVMs to know the answer to this. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
