I guess my issue was the undocumented (?) change in the current Hosts file if a "save as" was performed. Since a little mistake on the part of a team member could (and did) have huge issues in the production environment, I think I would just have a global setting for where SA should currently get the host file, and make the 'save as' only that, a way to save off a copy of the current Hosts info. That way a change is more deliberate, and multi step. I don't think this issue is justification enough for rights/permissions to SA. Just a little more "stupid proofing" would be nice.
Mike >>> [EMAIL PROTECTED] 11/04/03 12:16PM >>> Authentication is a complex subject and tough to get right. The users need to use it correctly, the admin needs to configure it correctly, etc. I would hate to see SA development slowed by trying to add this which is outside its core functionality. I think Host file versioning of some sort would be helpful. Doing a "Save" would rename the existing file and save the new file to hosts.cfg. The backup file names could include the date and revision(20031104001.cfg) or something similar. -Kevin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx > Sent: Tuesday, November 04, 2003 11:39 AM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Hosts file... > > The question that pops to my mind is, what should be changed > in SA to be able to cope with this siuation? > People need to logon to Servers Alive in order to make a > change? And each user can have different rights? Great and > what if a user doesn't do a log-off then somebody can make a > change under his/her account? > An application can try to do a lot but at the end we have to "trust" > that people know what they are doing. > > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Stone > Sent: Tue Nov 04 5:35 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Hosts file... > > > Usually opening the Save or Save As dialogs will take you to > the same directory that was last used. You have a > procedural/policy issue that you need to sort out as to who > updates and how it is documented. > Programming will never overcome that. > > To be honest I get the feeling you should be looking at a > package other than Servers Alive. I work in an environment > that SA fits pretty well, your environment seems to have > requirements that are outside the scope of SA at this point. > I have no doubt that Dirk will get there but until then one > of the larger and unfortunately much more expensive packages > might work better for you. > > -Kevin > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook > > Sent: Tuesday, November 04, 2003 10:32 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [SA-list] Hosts file... > > > > That's all lovely for a single person team who can remember that > > they've changed the current host file. My current issue is > with how to > > find out where SA currently thinks it is saving the data. > The supposed > > correct host file is not being updated, and since I can't > tell where > > it IS being updated, I can't find out if there is something > wrong or > > not. While I may not agree with the programmers philosophy > of how this > > should work, that doesn't really matter. Still, I am in a bit of a > > pickle. :) > > > > Mike > > > > >>> [EMAIL PROTECTED] 11/04/03 09:54AM >>> > > Well let's see. You have a working Salive & Host file. Your > adding new > > checks and services. If you do a Save, you've just up-dated your > > WORKING host file. If you do a SAVE AS, you have now save it to a > > different file name. You do this so you can get all the > buggs out of > > your host file before you make it your Start Up host file.. > > ----- Original Message ----- > > From: "Michael Shook" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, November 04, 2003 9:19 AM > > Subject: RE: [SA-list] Hosts file... > > > > > > "by hand" I meant File | Save > > > > Why would you want that to be the case? You have a place in > the setup > > for where the host file is, why ever would you want to > change the file > > name of the host file and not show that it has been done? How do I > > know what the file name is when another team member decides > they want > > to grab a copy of the file? How would I know it's been > changed without > > expressly looking for it? > > > > Mike > > > > >>> [EMAIL PROTECTED] 11/04/03 09:00AM >>> > > Once you do a save-as that becomes the "new" name of the file and > > that's what SA will use then when you do a save. > > Same situation if you would do a save-as in word for example. > > > > What do you mean "update by hand?" > > > > > > dirk. > > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > > Behalf Of Michael Shook > > Sent: Tue Nov 04 2:54 PM > > To: [EMAIL PROTECTED] > > Subject: [SA-list] Hosts file... > > > > > > I just saved a copy of the hosts file to a different file > name in the > > SAlive folder. Then for other reasons, that file was renamed and > > placed elsewhere. Then I closed SA after a few minutes. I > then noticed > > that the file I just "saved as" was created and updated. > The 'normal' > > host file was not. > > > > Also, I am experiencing trouble with the usual hosts file. > Ever since > > yesterday when I started working with a check that had an 'unusual' > > schedule (no check between 15 and 30 minutes after each hour, each > > day), the HostsFile isn't being updated unless I do it by hand, and > > some status changes aren't being written to the database. > > > > Any Ideas? > > > > > > Michael Shook > > Business Continuity Analyst > > Saddle Creek Corporation > > 723 Joe Tamplin Industrial Blvd > > Macon GA 31217 > > 478 742 8740 ext. 105 (work) > > 478 256 9318 (mobile) > > 478 742 7917 (fax) > > [EMAIL PROTECTED] > > http://www.saddlecrk.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 > > > > 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 To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
