OK. I didn't realise that, although I suppose it's obvious in hindsight. I just saw the potential for it to go wrong if that "localhost" check failed, and disabled it. I didn't actually test whether it could be shutdown from another host.
> -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Wednesday 29 September 2004 21:26 > To: Tomcat Users List > Subject: RE: Using shutdown script for different port > > > > Hi, > You must have a weird setup... The shutdown socket only accepts > connections from its localhost. > > Yoav Shapira > Millennium Research Informatics > > > >-----Original Message----- > >From: Steve Kirk [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, September 29, 2004 4:22 PM > >To: 'Tomcat Users List' > >Subject: RE: Using shutdown script for different port > > > > > >To be clear, the default setup _does_ allow shutdown using > telnet from > any > >machine unless your host or network security blocks it. Or at least > that > >was the case when I installed mine. > > > >I have the shutdown feature disabled on my setup because I > didn't like > the > >possible security hole. However I suggested it because I imagined you > had > >already secured the shutdown port using firewalling but were looking > for a > >way to stop each instance from the localhost. > > > >> -----Original Message----- > >> From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday 29 September 2004 21:11 > >> To: Tomcat Users List > >> Subject: RE: Using shutdown script for different port > >> > >> > >> > >> Hi, > >> Of course, you can only do this telnet from the local machine ;) > >> Otherwise we'd have a nice security hole ;) > >> > >> Yoav Shapira > >> Millennium Research Informatics > >> > >> > >> >-----Original Message----- > >> >From: Steve Kirk [mailto:[EMAIL PROTECTED] > >> >Sent: Wednesday, September 29, 2004 4:10 PM > >> >To: 'Tomcat Users List' > >> >Subject: RE: Using shutdown script for different port > >> > > >> > > >> >You can certainly telnet to the shutdown port and send > the shutdown > >> string. > >> >You could do this using a scripting tool or simple Java class. For > >> example, > >> >telnet to localhost 8015 then send the string "shutdown", or > whatever > >> >string > >> >is configured in server.xml for that port. > >> > > >> >> -----Original Message----- > >> >> From: Dhruva B. Reddy [mailto:[EMAIL PROTECTED] > >> >> Sent: Wednesday 29 September 2004 20:21 > >> >> To: tomcat > >> >> Subject: Using shutdown script for different port > >> >> > >> >> > >> >> I am running two instances of Tomcat 4.1 on one machine, from a > >> common > >> >> installation (i.e., different CATALINA_BASE). I have > the shutdown > >> >> service for each instance listening on a different port (the > >> original > >> >> instance on the default port of 8005, and the second instance > >> >> on 8015). > >> >> > >> >> Getting the instances to listen on a different port was > easy, but > I > >> >> can't seem to find any information on how to actually specify a > >> >> non-default port in the shutdown script. Some documentation > >> >> that I did > >> >> manage to find suggested the following would work: > >> >> > >> >> shutdown.sh port 8015 > >> >> > >> >> but I get the usage message when I try that. > >> >> > >> >> Can anyone tell me how to do this? > >> >> > >> >> Thanks, > >> >> Dhruva > >> >> > >> >> > >> >> > >> >> _______________________________ > >> >> Do you Yahoo!? > >> >> Declare Yourself - Register online to vote today! > >> >> http://vote.yahoo.com > >> >> > >> >> > >> > --------------------------------------------------------------------- > >> >> 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] > >> > >> > >> > >> > >> 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] > >> > >> > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
