Does anyone know the way to modify the notes.ini so that Domino names the log.nsf to log(month, day, year).nsf so that if a program does “restart server” each day a new log.nsf will appear with that days date?
I think I am close to finding the answer in the subject line but it isn’t there yet.
You might instead bring a hammer to work and hit yourself over the head with it repeatedly, which has about the same ratio of benefit to drawbacks as keeping a separate log database for each day.
If you have a single log database, then you have one place to search for any events that may have happened recently. Say you have a scheduled agent that posts a log message when it runs, once every two weeks or so – when did it last post that message? How many separate databases do you want to have to search through to answer this question? Did you route a mail message to a particular domain sometime in the last month? Good luck finding out.
All sorts of tools that are available to do log analysis, assume they’re scanning a single database – not a set of databases with similar names.
If there is some goal you’re trying to accomplish by this, you might tell what it is – there’s probably a better way.
If you really must… I don’t know whether there’s an ini variable. If not, let the current day’s log be called log.nsf. If a program does restart the server, that program could create a new database log.nsf and copy all the documents over from log.nsf (except the most recent) and then delete them all (except the most recent).
A file copy of log.nsf to a new path is inadvisable because it keeps the same replica ID, and a new database has the old name but a different replica ID, which causes confusion in the Notes client as to which database a bookmark or workspace icon really points to.
I didn’t get into details about what I need the log for but it has to do with being ordered to keep a copy of all the logs for about a three month period. I did this once before and didn’t document what I did since I didn’t think I would have to do something like this again.
Yes I posted this before and with some of the people out there who are bright I figured someone would finally see a post and give me an answer. As you could tell, well maybe not you, as most people could tell I normally don’t repeat myself even when I don’t get an answer but I am under some pressure to get this done, I don’t want to manually do it and I want to be able to undo it when I am done.
I can’t believe just how many arrogant jerks there are in this forum.
I’m sorry that my whimsical way of expressing myself has offended you; next time you ask about the proper way to attach a solid-fuel booster rocket to the top of your car to boost your speed, I’ll just shut up with the advice about whether it’s a good idea, and tell you where to attach the struts.
it has to do with being ordered to keep a copy of all the logs for about a three month period.
That’s the kind of information I was fishing for. You don’t need a new log database for every day, you just need a running copy of three months’ worth of log entries. Is there any reason you can’t just keep them in the log.nsf database?
If there is a reason to use a separate database, it’s much easier to keep using the same log database and just copy out the information you need. Why you want to have a separate database for each day, I still don’t know, but you could do this with a daily scheduled agent that scans the views of log entries, finds all those that have an end time of yesterday, and copies those documents to a new database created from the log template. I’m sorry I don’t have time to write the code for you, but if you could take a stab at it and post here again – to this thread – if you get stuck, then I would be willing to help get you unstuck.