Bob,

Well I'll let you in on a little known secret about Sesame's Log Reader/Writer.  Next time you get a log file from a client name it s_log0001.log and Sesame will open that file instead of the s_log0000.log. You see the log reader and writer looks for the highest # existing log file and opens that file, hence why there are 0's after the name. So you only need to save the log file sent to you as a new name one higher than the last one and once you are done delete it. It is important that you do not skip numbers.

Now one of the things that I did here, since I look at logs every day, is I had a seperate directory for Sesame Logs. I put a Sesame Executable in there and run it only to read the logs in there. That executable had no access outside of that directory so it did not affect my normal log files nor could it be used for anything other than reading logs.  When I got a new log from a client I would just name it one higher than the last one and Sesame would read that one when I was in Server Admin.

But I will look into it and see what can be done about the Load and possibly the Save As.

-Ray

If I ever finish it up and decide to pack it up, there will be an even simplier solution, an external Log File Reader that can accept a log file name as an argument. I have already built a crude one for personal use and I use it more than I use the Server Admin window.

-Ray

Text readable log files means Text editable log files and the log files are the one way that Tech support can see what you have been doing and what has been happening.  The log files may contain tell tale signs of a few things that the user either did not see happen or neglected to tell me about.

but on to your question. The current log files are not encrypted and you can open them in any Text Editor, Don't save them in it though. They will look odd as the files have to follow a particular format as the log files are circular and will wrap at 10,000 entries, in the current logs. They will also look odd as they are binary files, but you can see the date and time stamp, the error code and the details of the error.

If I have anything to do with it the next major version of the Sesame will have an encrypted log file because I have already recieved a log file that had an entry removed in it and it had been edited in an ASCII editor.

-Ray

You are correct, the Log file with the missing line did not come from you. I apologize if I implied that it was from you.

If I password protect it who gets the password?
Read-only is too easy to turn off.

The thing is I depend on those log files every day, they help me do my job faster and more efficiently. When someone does not have it, or it has been changed, it slows me down. So I naturally do everything in my power to protect those files and if I have the option to go to encryption on those files I will do it in a heartbeat. I see no reason not to encrypt them. The only reason I can think of is so that people can open them in an ASCII editor. As of right now the current logs when opened in a Text Editor are going to be hard to read until you replace some characters and tidy them up. Even then if the user has had more then 10,000 errors the log file will have wrapped and you would not be sure where the wrap ends/starts as it may be in the middle of the file.

-Ray

CRC sounds good, but no need to go too far. 

My original request  to be able to choose which files to open and read is most important.  As long as I have a viewer and ability to Save As and/or Print, then I will be content, ReadOnly, encrypted or not.

Right now I print to PDF document, Save As text file from PDF, use text editor to clean up line enditngs and wrap arounds, and have a usable file to use with text editor from that point.

I agree, it is best not to allow changes to real logs, but having non Sesame copies to work with, adding notes, sorting, counting lines, etc. is helpful.

Did not know there was a 10K wrap.  I just finished working with a 7.5K, but typical translations lines have many duplicates of same error trigger. 

Quote:
Another undocumented tool?

I have used some combinations of Server_Note, Server_Warning, Server_Error, Client_Note, Client_Warning, Client_Error, and No Filter. 

Never heard of Severity Filter..........???



Oops and Ah Ha! ..... 
Those are the Severity Filters!  I just noticed the label at the top of the column - Severity. !  I though you were talking about another filter category that was not listed.

So I guess the answer to your question is YES.

Would like ability to SaveAs the normal Sesame log format as a minimum.  That will allow to save in other folders from default.  Changing number in the name may be a problem if opened up in normal Viewer if not the correct sequence number?  Would be good to possible change name, but don't wnat to cause a problem.

Would also like ability to read in text format.  But I know there are many "standard" text formats, so I would say DOS text format (but Mark will prefer Unix text format, I understand).
That will allow easy access to do anything, use any naming convention, etc.