Running scripts on the linux box is probably your best bet. Dirk had a nice external app that would do telnet and ssh connections to a remote box, but the app I have included with my version now is telnet only. Perhaps you can get the ssh version from Dirk and use that to run your remote script to check up on java.
Mark Bradshaw Salem Web Network [EMAIL PROTECTED] 9401 Courthouse Road, Suite 300 Chesterfield, VA 23832 804.768.9404 x100 > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of David Buckland > Sent: Tuesday, June 24, 2003 5:36 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Linux monitoring > > > Thanks Mark and the others for your suggestions. > Its mainly Tomcat and Java that sometimes have trouble. Tomcat is easily > checked via the application URL's or the Web manager app. > Slightly indirect > but it sounds like the simplest. It will also secondarily show > issues with > the Web server, although thats never been an issue to date. > Java is actually usually what bogs Tomcat (its amazing what users > try to do > sometimes) but thats a bit more obscure to check. Suggestions around that > and anything else people have found useful would be great. > David To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
