yep it will save them (that is IF the service has write access to that file :-))
Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 1:51 PM To: Servers Alive Discussion List Subject: RE: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times Ah! Got you now. So, just to be absolutely clear: IF SA is running as a service, AND the "Save Changes..." option is set, AND the entries filename is known, THEN changes will automatically be saved? Great! Had me worried for a minute... ;-) Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 "Dirk Bulinckx" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 27/02/2007 12:35 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject RE: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times I think I didn't explain well what I wanted to say: SA running as service and "save changes.." option is NOT set -> changes are not saved and you are NOT prompted to do so -> all other cases IF you did a change then you will be asked if you want to save (or if the filename of the entries file is already known, then it will be saved to that file). SA running as app -> question if you realy want to quit SA runnign as service -> question if you realy want to quit is NOT asked Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 1:06 PM To: Servers Alive Discussion List Subject: RE: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times ??? Sorry, I've missed something critical here. Changes aren't saved automatically when running as a service? I don't understand the logic of that. We (and I would guess most people) run SA as a service, and if the changes aren't being saved then I'm in serious danger of losing changes whenever systems are rebooted for patching or whatever. Surely if you don't want this, you should untick the option? Am I misunderstanding this? Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 "Dirk Bulinckx" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 27/02/2007 11:45 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject RE: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times Service: this was requested by our uses to NOT have this when running as a service; making a change -> FILE-SAVE. Priority: if you make a change to the setup and it's not saved, then OR you're running service and app at the same time and looking at the service that kept running while doing the change in the app OR you're not running as a user that has admin rights on the local system. RRD: each time you add entries to Servers Alive you need to create a new db for each of those entries. There is an RRD file per entry. Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Danijel Brncic Sent: Tuesday, February 27, 2007 12:36 PM To: Servers Alive Discussion List Subject: AW: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times Hello Dirk, thanks first for fast reply :) Service: In the Setup/General/Misc Settings you can check "Automatically save changes on exit (to a file). This worked on the old Server when SA was not configured as Service. When I now e.g. add an entry and restart server or SA service, the changes are not being saved. Priority: Logging to log file is disabled. I tried to turn it on, but every time I enter needed data into setup/logging/Logfile/to file and save that, nothing happens. When I check again these settings, logging is again disabled and all parameters are set to default!? I imported the hostfile and reg entries from the old server, there SA was installed on c:, now on d:! Probably there's a problem...? RRD: I checked this again and there are now really both times added. What I found out is, that when checks are stopped and then the RRD DB is created, SA writes only the "checks-done-value" without adding the duration (as it was in my case). When checks are started, both values are added! So this means also, when adding some new checks the RRD DB should be recreated?! -------------------------------------------------------------------------------- Von: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag von Dirk Bulinckx Gesendet: Dienstag, 27. Februar 2007 10:26 An: Servers Alive Discussion List Betreff: RE: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times Service: what exact setting are you talking about? Priority: what does the logfile show as reason for not checking those entries? RRD: did you have SA create the "create" file before it did a checkcycle? SA will use the interval time + the time it took to do a checkcycle (that is IF a checkcycle was already done). Dirk Bulinckx. -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Danijel Brncic Sent: Tuesday, February 27, 2007 10:16 AM To: Servers Alive Discussion List Subject: [SA-list] SA as Service, no automatic change saving on exit / priority / RRD + check times Hello @ all, We updated SA to v6 and moved it to a new Server, both worked fine! But I have three questions: SA Service: Now SA runs as a service on a Win XP Machine. I experienced, that the automatic change saving to the host file is not working now. When I restart the service all changes are gone... Is this common and/or intended? Priority: Some checks are done with priority "1 of 100" and "start cycle 1". When I start SA, some of those are checked in the first cycle, other not though all are configured identically. Where could be the problem? RRD + checktimes: Our checks are running every one minute. So, SA makes a round (takes about one minute). Then RRD Data is written. After that SA waits one minute to start a new cycle. In the sa_Create_RRD Script the parameter for the check cycle is set to 60 sec. Isn't this wrong because of checks are done as described every two minutes?! TIA Danijel Brncic -------------------------------------------------------------------------------- Sitz der Gesellschaft: AMADEUS FIRE AG Darmstädter Landstraße 116 60598 Frankfurt am Main Aufsichtsrat: Gerd von Below (Vorsitzender), Hartmut van der Straeten Vorstand: Günter Spahn (Vorsitzender), Peter Haas, Dr. Axel Endriss Amtsgericht: Frankfurt am Main HRB 45804 -------------------------------------------------------------------------------- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten dieses Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail contains confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------------------------------------------------- Sitz der Gesellschaft: AMADEUS FIRE AG Darmstädter Landstraße 116 60598 Frankfurt am Main Aufsichtsrat: Gerd von Below (Vorsitzender), Hartmut van der Straeten Vorstand: Günter Spahn (Vorsitzender), Peter Haas, Dr. Axel Endriss Amtsgericht: Frankfurt am Main HRB 45804 -------------------------------------------------------------------------------- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten dieses Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail contains confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
