Q1: if there is no subject in the registry it will default back to a hard-coded subject. Q3: you mean SSL FTP?
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Sun Feb 09 7:10 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Couple of Bugs, and a Couple Questions? Q2: Well, it worked. I would guess that it is because I had already cleared the alert subjects in the host file -- which makes me question where it got the default subject if I hadn't entered it in the registry yet? Q3: Has anyone ever implemented SSL on the Web page upload (via FTP). Sure hate sending clear-text password. I suppose this could be scripted outside of SA as long as the script would die/retry if the local HTTP file was open by SA following an update. Thanks, JV. -- Jim Vaughan FAX: 402-399-3533 Information Services / Telecommunications & Networking Central States Health & Life Co. of Omaha - http://www.cso.com |---------+----------------------------> | | "Dirk Bulinckx" | | | <[EMAIL PROTECTED]| | | u> | | | Sent by: | | | salive-owner@wood| | | stone.nu | | | | | | | | | 02/08/2003 04:44 | | | PM | | | Please respond to| | | salive | | | | |---------+----------------------------> >--------------------------------------------------------------------------- ---------------------------------------------------| | | | To: <[EMAIL PROTECTED]> | | cc: | | Subject: RE: [SA-list] Couple of Bugs, and a Couple Questions? | >--------------------------------------------------------------------------- ---------------------------------------------------| Q1: no Q2: the subjects that you changed (as stated in your next mail) are for the DEFAULTS, this means for NEW entries. for the existing entries you'll have to change it within the hostfile dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Sat Feb 08 11:31 PM To: [EMAIL PROTECTED] Subject: [SA-list] Couple of Bugs, and a Couple Questions? In 'Advanced Options' under the 'Checking' tab, I've set 'Automatically restart checking after' to 60. and the form identifies the 60 as 'seconds'. However, in reality, the time period that Servers Alive waits before it restarts is actually 60 minutes. Also, under 'Setup' on the 'Startup' tab in the 'Other Startup Options' area, I've set the 'Cycle Unit' to 'Seconds' and set 'Check times (every x seconds)' to 30 for all hours and all days (weekday, Saturday and Sunday). On the main Servers Alive screen in the bottom left area, however, it reads 'Checks done every 30 minutes' until a full check cycle completes. This happens just after going into Setup and saving any changes I've made. Not a big deal, but confusing until you see what's going on. Question 1: If 'Send mail at start/stop' is enabled, Is there any way to force Servers Alive to send an eSMS formatted message instead of the long form that Servers Alive uses by default when it has been stopped or started? Question 2: Is there any way to control what Servers Alive sends in the eSMS alerts? I've set 'DefaultPrimaryMessage' and 'DefaultAlternateMessage' both to '%p %s', but the eSMS message still reads 'HOSTNAME is DOWN'. I don't have the word 'is' in there anywhere. Thanks, JV. -- Jim Vaughan FAX: 402-399-3533 Information Services / Telecommunications & Networking Central States Health & Life Co. of Omaha - http://www.cso.com To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
