For one, it bloats your log for no good reason. Second, the results could be split across multiple documents. And finally, other tell commands redirect to a txt file just fine. Why not the DAOS stuff?
Subject: re: How to redirect console output to file?
I’m just guessing…but it sounds like the “tell daos” command is doing something asynchronously.
For the results to be piped, the output needs to be a direct result of the command you issue. If, instead, the tell command you issue causes another command to be spawned that writes the output, then the piped output from the tell command would only show that information.
My guess is that may make it tough to get the output (you can try using a text console log file and parsing it…much easier than messing wtih the “nsf” log file).
I’m still on 8.0.2, so I haven’t messed with DAOS–but it may be that the tell command needs information from another server. Perhaps running it on a different server would provide a direct response via the tell command.
you can try using a text console log file and parsing it…
this is what I do now. I want to get the DAOS ticket counts. ( There is no business case, it is only experimental. Just to see, what is possible or not )
To redirect the output, I trigger a “start consolelog” from lotusscript followed by a tell daosmgr dbsummary. After this I close the consolelog with “stop consolelog”.
The Notes tool below generates DAOS reports including Logical, Physical and DAOS size. You can export to Excel, or schedule the reports to run daily, weekly or monthly which are saved inside a Notes app.
It also generates other reports below which assist a Domino Administrator to optimize server performance and even prepare for a messaging migration (i.e. IBM SmartCloud Notes Hybrid).
ACL Dominator 6.0 for IBM Notes and Domino
DAOS reports including Logical, Physical and DAOS size
Mailbox/App document count report (useful to identify mailbox/apps which require archiving)
Full Text Index reports (useful to optimize server performance by identifying non-critical mailbox/apps using “Immediate” frequency which should ideally be changed to “Hourly” or "Daily)
Mailbox delegation reports (useful for messaging migrations)
Mailbox user activity reports (useful to identify mailboxes which can be retired)
Group troubleshooting (useful to identify mailbox/app access issues using heavily nested groups)
Mailbox owner reports including changing owner ACL (useful to force mailbox access of all mailbox users to Editor) i.e. Specify “$$MailOwner” in tool when performing ACL updates
I’m in the same boat. I want to vector the output of ‘tell router o’ to a text file, but I can’t. Ulrich’s idea is slick, but we already do console logging, so I can’t start and stop it, and our log file is massive.